Team Management
Invite team members, assign roles, and manage permissions. FireBreath supports 5 roles with 9 configurable permissions for fine-grained access control.
Roles
FireBreath has 5 built-in roles:
- Owner — Full access to everything. Cannot have permissions reduced. One per organization.
- Admin — Full access by default, can be customized. Can manage team members and settings.
- Editor — Can create, edit, and schedule posts. Cannot manage team or settings.
- Reviewer — Can view and approve posts, but cannot create or edit them.
- Viewer — Read-only access. Can view posts, analytics, and calendar but cannot make changes.
Permissions
There are 9 permissions that can be customized per role:
- 1.view_posts — View posts, calendar, and dashboard
- 2.create_posts — Create new posts and drafts
- 3.edit_posts — Edit existing posts
- 4.delete_posts — Delete posts
- 5.publish_posts — Publish posts immediately
- 6.approve_posts — Lock/unlock posts in the review queue
- 7.manage_integrations — Connect and disconnect social accounts
- 8.manage_team — Invite members, change roles, remove members
- 9.manage_settings — Access organization settings and permissions
The Owner role always has all permissions and cannot be modified.
Inviting Team Members
To invite a team member:
- 1.Go to Settings > Team.
- 2.Click "Invite Member".
- 3.Enter their email address and select a role.
- 4.They will receive an invitation email with a link to join your organization.
Invited users who do not have a FireBreath account will be prompted to create one when they accept the invitation.
Customizing Permissions
Organization owners can customize permissions for each role:
- 1.Go to Settings > Permissions.
- 2.Toggle individual permissions on or off for each role.
- 3.Changes take effect immediately for all members with that role.
This allows you to create custom workflows. For example, you might allow Editors to create posts but require an Admin or Reviewer to approve them before publication.
Tips
Use the Reviewer role for stakeholders who need to approve content but should not create or edit it.
Keep the number of users with publish_posts permission small to maintain quality control.
The Owner role is a safety net — it always has full access, preventing accidental lockouts.