In CreatiBI, permissions control the level of access users have to view and edit information. This enables users to balance collaboration and control while ensuring that company data remains secure. For instance, when working on a confidential project, the project team should be able to collaborate, but the information should only be shared with those who need it.

Permissions mainly occur at the object level and are options that limit access to things like teams, projects, tasks, or creatives.

Object-based permission

Object-based permissions determine the type of access you have as a member depending on which team, portfolio, project, or task you've been invited to. Access is independent across teams, portfolios, and projects.

For example, if you add someone to a team, they can access all the projects in the team with public-to-team privacy settings. However, they can only view projects set to private to members of that team if they are invited directly to the project. Object-based permissions allow you to invite different collaborators to various teams or projects while keeping sensitive information hidden.

You can also add collaborators to a scriptwriting or media production task without adding them to the project where the task resides. These task collaborators won't have access to other tasks in the project. Project admin or project editor can give you access to view or edit projects if needed.

In CreatiBI, a single user can have multiple access levels, based on the content created and the permissions given.

Task permissions

Access to a scriptwriting task depends on the task's privacy setting (when a script is not part of any project, it is considered to be in a private state), and may also depend on the privacy settings of the project where the task lives. For a detailed overview of the scenarios where someone can access a script task, visit script task permissions directly.

Access to a media review task depends on the privacy settings of the project where the task lives. For a detailed overview of the scenarios where someone can access a media review task, visit script task permissions directly.

Project permissions

Projects have both public-to-team or private-to-member privacy settings along with three roles: project admin, editor, and commenter. These settings and roles enhance control over project data.

Click here for more guide to managing privacy and permissions.

Team permissions

Visit our team permissions article for the best insight into team privacy and sharing, including the team admin roles.

Organization and workspace access

Organization is only accessible by CreatiBI users who have signed up for an account with their company email address, or were specifically invited into an organization. Admins can control invite settings via the admin console.

Workspace is only accessible by CreatiBI users who have been invited into the workspace by a current workspace member.

Admin rights

The admin console is where admins can manage CreatiBI for your organization. Admin console provides an accurate count of the members, guests, and pending invites. Also included are security options and provisioning controls. This allows you to easily add or remove users as needed, giving you complete control over your organization's members from a single, central location.

Guest permissions

Guests are users that don't share the organization's email domain. Guests can only access what is shared with them. Use guests to collaborate with clients, contractors, or anyone without an approved organization email domain.

Like what you see? Get started with a free 30-day CreatiBI trial today. Try for free.

Last updated