Skip to main content

Role-Based Permissions for Invited Users

Currently, invited users have full access to critical account functions, including the ability to remove connected social accounts and view license information. This creates unnecessary risks and reduces control for account owners.

Proposed Solution:
When inviting users, introduce role-based permissions with two clear options:

  • Admin (Full Access): Complete control over account settings and connections.

  • Editor (Limited Access): Ability to create, edit, schedule, and delete posts for assigned profiles, but no access to account connections or license details.

This feature ensures better security, privacy, and clarity when collaborating with team members.

Status: Completed4 comments

Log in to comment and vote

Comments4

  • Miquel Palet López

    Team•

    Jul 13

    Good news, role-based permissions for invited users are supported!

    When you invite a team member you assign a role (owner, admin, billing admin, member, or viewer), and each role maps to an enforced set of permissions. You can also scope a member to specific profiles only. For example, a viewer gets read-only access within their profile scope.

    Caveat worth flagging: roles are a fixed preset rather than a fully custom permission builder.

    Details here: docs.zernio.com/invites/create-invite-token. Thanks for the request!

  • Simon Coton

    •

    Jul 11

    To go with this - permissions on a member should enable “draft-only" so it lets a member create drafts but blocks them from publishing/scheduling directly to the platform before approval.

    Right now the workaround is:
    - members create drafts and leave them for you, then you review + publish/schedule from your login (informal, not enforced) - they can still publish if they want to

  • Dalek

    •

    Dec 3, 2025

    I would like that proposed admin permissions to be still restricted to the assigned profile however

    a “Profile admin” perhaps if you will

    And a “global admin” for ourselves and others we deem to need such high level permission

    I would also request a transition period for permissions, or defaulting all existing users to the proposed “editor” level scope and have us adjust, I think it would be wise to have any existing users becoming the global admin permissions level

  • Anna Cumi

    •

    Nov 4, 2025

    Following the proposal, create a review role and choose which profile will have access to it. This would be useful for sending schedules to clients so they can review them. With this role, it would be interesting if they could write comments for community managers.