Role
Terakhir dikemas kini pada
11 Mei 2026
Learn how projects let you collaborate and stay aligned in a shared workspace.
Roles and access determine who can view, edit, organize, or manage content. Projects, with more sharing capabilities, enhance collaboration among Adobe users by allowing them to share multiple assets in bulk with the same group rather than individually.
Roles in projects
Projects use role-based access. Each collaborator is assigned one role that defines what they can do within the project.
|
|
Capabilities |
|---|---|
|
Editor |
Can edit, download, and share |
|
Commenter |
Can view and comment |
Access
Access controls who can view a project. While individual accounts only allow invited people to access a project, there are two levels of access for enterprise accounts:
|
Access level |
Who can access |
Default role |
|---|---|---|
|
Everyone at [organization] |
All members of your organization |
Commenter |
|
Only invited people |
Specifically invited users |
Depends on the assigned role |
Currently, projects can only be shared at the organization level for enterprises. However, individual files within a project can still be shared publicly, offering more flexibility for specific assets.
Within projects, inheritance means that any file or folder within a project automatically adopts the same access and permissions as the project itself. This creates a consistent permission structure where project-level access flows down to all the files within it.
Creative Cloud’s collaborative ecosystem consists of multiple hierarchical levels, each with specific purposes:
- Organization: Connect Teams and Enterprise users within a shared collaborative space.
- Project: Bring together related files and folders into an easily shareable repository.
- Folder: Help organize files within a project.
- File: Save creative assets such as design, documents, and media.
Each resource inherits the access and permissions from the project. By default, files and folders take on the same access settings as the project. You can promote access at a lower level (such as giving someone editor access to a specific file), but you can’t demote it. If someone has editor access to a project, they’ll retain edit access to all content within it.
Example: If a team has commenting access to a project, you can individually promote certain users to edit specific files. However, if someone already has edit access to the project, you cannot restrict them to only commenting on a single file.
Terokai Adobe Creative Cloud
Kemas kini, naik taraf atau cari aplikasi baharu.
