Project permission
Last updated
Last updated
In CreatiBI, if someone (excluding guests) has access to a project, he can have access to all tasks and messages within it.
See the table below for a quick overview of how different project privacy settings determine which users can access a project.
Private to members
Project member
Public to team
Team member and project member
The "Private to Members" privacy setting for a project limits access exclusively to current project members and those invited in the future. Under this setting, individuals not part of the project must seek permission to join. Additionally, projects with this privacy level won't appear in search results for non-members.
The "Private to members" privacy setting is available for CreatiBI's Buseinss plan and above.
Public to team is a project privacy setting that grants access to the project to members of the team in which the project resides. With this privacy setting, all members and invited members of the project's team can access the project.
The comment-only permission is available for CreatiBI's Advanced plan and above.
Comment-only permissions for projects allow users to view or comment on projects without giving them access to edit them. This makes it easier to share the information in a project with anyone that needs it, while preventing any accidental or unnecessary changes.
You can access permission settings through the "Share" button on the project page.
Only project members who have project admin or editor permissions can modify a comment-only project. Those who are not project members may still have access to the project as a whole or to any of the individual tasks within it, but will only be able to access the project with comment-only permissions.
Not only can you set permissions for individual members, but you can also control the access permissions for task collaborators within the project and the members of the team to which the project belongs.
To change a project member's permission settings:
Click on the drop-down menu beside the name of the project member you are changing the permission settings for;
Select "Project admin" to give them full project permissions, including deleting the project, "Editor" to give them edit permissions, or "Commenter" to limit permissions to comment-only;
Close the menu to save your changes.
If a user has been assigned two different access levels in a project through different roles, CreatiBI will automatically assign the highest level of access they are entitled to across these roles.
For instance, if Alex is granted "Commenter" access when he joins a project, but as a member of the design team, he is entitled to "Editor" access, then his "Editor" access will have priority over the "Commenter" access.
The table below outlines the capabilities of project members with "Project admin", "Editor", and "Commenter" permissions:
Rename project
✅
❌
❌
Modify project description
✅
❌
❌
Set project status
✅
❌
❌
Move project to a different team
✅
❌
❌
Control project permission
✅
❌
❌
Delete project
✅
❌
❌
Change project privacy
✅
❌
❌
Set project icon
✅
✅ (If admin allows)
❌
Create / delete share links
✅
✅ (If admin allows)
❌
Add and modify workflow features
✅
✅ (If admin allows)
❌
Manage project member and member permission
✅
✅ (If admin allows)
❌
Add project to portfolio
✅
✅
❌
Modify project overview
✅
✅
❌
Set default project tab
✅
✅
❌
Add/edit scriptwriting task
✅
✅
❌
Edit script content
✅
✅
❌
Comment and reivew script
✅
✅
✅
Add/modify media review task
✅
✅
❌
Comment and review media
✅
✅
✅
Add/modify creative
✅
✅
❌
Add/modify table field value
✅
✅
❌
Publish creative
✅
✅
❌
Check data insights
✅
✅
✅
Add/modify custom field
✅
✅
❌
Add/modify custom rule
✅
✅
❌
Add/modify app integration
✅
✅
❌
Like what you see? Get started with a free 30-day CreatiBI trial today. Try for free.
