Faqify uses a three-tier role system to manage team access and permissions. Understanding these roles helps you set up your team effectively and maintain security.

Role Hierarchy

Owner

The highest level of access with full platform control.

Permissions:

• Full platform control and team management
• Can manage all team members and their roles
• Can promote users to any role including Owner
• Can delete the company
• Cannot be removed from the company
• Cannot demote themselves if they're the only owner

When to Use:

• Company founders and business owners
• Primary account holders
• People who need complete control

Admin

Mid-level access for content management and team collaboration.

Permissions:

• Can invite and add new members (default to Member role)
• Can remove Members and other Admins (but not Owners)
• Can promote Members to Admin
• Can demote Admins to Member
• Cannot modify Owner roles or promote to Owner
• Can demote themselves to Member
• Can update company information
• Cannot delete the company

When to Use:

• Content managers and team leads
• People who need to manage team members
• Senior team members who don't need full control

Member

Basic access for article review and editing.

Permissions:

• Can view company information and team members
• Can review and edit articles
• Can create manual articles
• Cannot manage other members or change roles
• Cannot modify company settings
• Cannot invite or remove team members

When to Use:

• Content creators and reviewers
• Team members who only need article access
• New team members starting out

Role Assignment Guidelines

Starting New Team Members

• Default to Member role for new invitations
• Allows them to learn the platform safely
• Can be promoted later based on needs

Promoting Team Members

• Member → Admin: For content managers and team leads
• Admin → Owner: Only for company founders or primary stakeholders
• Any → Member: For demotion or role changes

Role Changes

• Changes take effect immediately
• Users are notified of role changes
• Previous permissions are revoked instantly

Permission Matrix

*Owner can only demote themselves if there's at least one other Owner

Security Features

Owner Protection

• Owners cannot be removed from the company
• Prevents accidental loss of company control
• Ensures someone always has full access

Last Owner Protection

• The last owner cannot demote themselves
• Prevents company from becoming unmanaged
• Requires promoting another user to Owner first

Admin Restrictions

• Admins cannot touch Owner roles
• Prevents unauthorized escalation
• Maintains clear hierarchy

Self-Demotion

• Admins can demote themselves to Member
• Useful for role reassignment
• Allows graceful role transitions

Best Practices

Role Management

1. Start Conservative: Begin with Member role for new users
2. Promote Gradually: Move users up based on demonstrated need
3. Document Roles: Keep track of who has what role and why
4. Regular Review: Periodically review role assignments

Security

1. Limit Owners: Keep Owner role to essential personnel only
2. Monitor Changes: Track role changes and their reasons
3. Train Team: Ensure team members understand their permissions
4. Backup Access: Always have at least two Owners

Team Structure

1. Clear Hierarchy: Establish clear reporting relationships
2. Role Documentation: Document what each role can do
3. Training: Provide role-specific training
4. Communication: Keep team informed about role changes

Troubleshooting

Can't Change Roles

• Verify you have permission to change that role
• Check if you're trying to remove the last Owner
• Ensure you're not trying to remove yourself
• Contact support for assistance

Permission Denied

• Check your current role and permissions
• Verify the action is allowed for your role
• Contact your account Owner or Admin
• Review the permission matrix

Role Confusion

• Review the role descriptions
• Check the permission matrix
• Contact support for clarification
• Ask your team lead for guidance

Related Articles

• Inviting Team Members
• Managing User Roles and Permissions
• Team Collaboration Best Practices