Skip to main content

Roles and Permissions

Which user roles and access permissions are available in contentbird?

S
Written by Sophia Siddig
Updated today

#admin #roles #permissions


Introduction

Roles and permissions in contentbird determine who can see and do what. They ensure clear responsibilities, secure processes, and structured collaboration within your team.


Standard Roles in contentbird

πŸ‘‘ Admin

Access: Full access to the entire system

Typical responsibilities:

  • Account setup

  • User management

  • Defining roles and permissions

  • License and billing management


πŸ“Š Manager

Access: All or selected projects

Typical responsibilities:

  • Campaign planning

  • Strategic management

  • Overview of content and team activities


✍️ Author

Access: Assigned content and tasks only

Typical responsibilities:

  • Creating content

  • Executing briefings

  • Working in the editor and with AI features


πŸ‘€ Observer

Access: Read and comment

Typical responsibilities:

  • Providing feedback

  • Reviewing content

  • Supporting approvals

πŸ’‘ Special note:
Observers are free of charge and can be used without limitsβ€”ideal for:

  • stakeholders

  • internal departments

  • clients


Creating Custom Roles

For more complex setups, you can define custom roles.

πŸ”§ When is this useful?

  • Large teams with clearly defined responsibilities

  • External service providers or agencies

  • Specific requirements (e.g. analysis-only or AI-only access)


Project-Based Roles & Secondary Permissions

In contentbird, roles are not only defined globally but can also be assigned per project.

πŸ‘‰ This means a user can have different roles depending on the project
(e.g. Manager in Project A, Observer in Project B).

In addition, you can assign secondary permissions:

  • Control extended access rights per project

  • Enable specific features (e.g. analytics or social features)

  • Adjust responsibilities without changing the main role

πŸ‘‰ For example, you can grant a Manager additional permissions in a specific project without modifying the global role structure.


What Permissions Can You Control?

With custom roles, you can define permissions in detail:

  • πŸ” Visibility: Which areas are accessible (planning, analytics, settings)

  • ✍️ Actions: Read, edit, delete, publish

  • πŸ“ Projects: Access to specific projects


Best Practices

  • ❌ Do not grant delete permissions to operational roles

  • βœ… Assign AI access selectively based on roles

  • πŸ“Š Limit analytics access to authorized users

  • πŸ”’ Start with restrictive permissions and expand if needed

  • πŸ”„ Regularly review and adjust roles


Conclusion

Roles and permissions are the foundation for secure and efficient work in contentbird. With clearly defined access rules, you ensure that everyone on your team uses exactly the features they needβ€”no more, no less.

Did this answer your question?