Roles and Permissions

Roles and Permissions: Decide What Each Team Member Can Do

RecurPost roles decide what each team member can open and change inside a client workspace. A role is a named bundle of permissions, and you give a member one role per workspace. The same freelance writer can hold Writer on one client and Editor on another, under a single login.

No credit card required

RecurPost includes roles and permissions on every plan.

AT A GLANCE

The four roles RecurPost supplies

RecurPost supplies four role templates: Contributor, Writer, Editor, and Publisher. Each one adds to the one before it. RecurPost labels a role built from a template “default” and a role you build yourself “custom”.

Contributor

Built for freelancers, interns and guest writers. Baseline: writes and edits its own posts, adds media, uploads to the content library, deletes its own posts, and sends drafts for review.

Still cannot: reach another member’s work. Approve. Publish or schedule.

Writer

Built for core content creators. Adds editing other people’s posts, and replying to comments and DMs in the inbox.

Still cannot: publish or schedule. Approve or reject.

Editor

Built for quality and strategy oversight. Adds approving or rejecting posts at review stages, deleting anyone’s posts, managing library timeslots and content, assigning inbox conversations, and viewing reports.

Still cannot: publish or schedule. Manage social profiles. Invite or remove members.

Publisher

Built for senior managers who run the content operation. Adds every permission in the catalogue, including publishing and scheduling, managing social profiles, exporting reports, DM automations, boosting posts, client review, workspace settings, and inviting or removing members.

Still cannot: open the Roles and Permissions page. That stays with the account owner.

ONE WORKSPACE AT A TIME

A role is a named bundle of permissions, and it applies to one workspace at a time

A RecurPost role is a named bundle of permissions that decides what a team member can open and change inside one workspace. You create a role once on the account and reuse it across every workspace you own. RecurPost then assigns that role per workspace, so a member holds exactly one role in each workspace they belong to.

The per-workspace part is the mechanic worth understanding first. RecurPost attaches the role to the pairing of member and workspace rather than to the account, so one person carries different authority on different clients without a second login and without a second seat.

RecurPost gives the account owner every permission in every workspace they own, with no role assigned. Team members cannot open the Roles and Permissions page and cannot change their own permissions. The owner makes every change.

A RecurPost role decides what a member can do. Giving them a separate workspace per client decides which accounts they can do it to. Those are two separate controls, and you set both.

In practice: A freelance social media manager working three clients for one agency shows the shape of it. The agency gives that person Writer on two client workspaces and Editor on the third. One login, three workspaces, two levels of authority.

The four RecurPost role templates - Contributor, Writer, Editor and Publisher - beside a custom role being built from individual permission switches

RecurPost role templates: Contributor, Writer, Editor, Publisher.

Fits

An agency where the same people work across several clients at different levels of trust.

Adds nothing for

A solo operator on one login, who has no second party to scope.

FOUR TEMPLATES

RecurPost role templates stay editable, and the Contributor-to-Writer line decides most hires

Each template adds to the one before it, and the cards above show where each stops. Treat the four as starting points rather than fixed tiers.

Starting points, not fixed tiers

Every switch inside a template stays editable after you create it, so an Editor who also publishes is a two-click change rather than a support request. RecurPost also lets the owner duplicate a role, which copies its permissions and notification defaults under the name “<role> (copy)”.

Why it matters: the four templates are a starting configuration, not a fixed set of tiers.

The boundary that decides most hires

The boundary that decides most hiring decisions sits between Contributor and Writer, and it is not the one people expect. A RecurPost Contributor cannot reach another member’s work at all. A RecurPost Writer can edit it. Neither can publish.

The real question on day one: not whether the new person should publish, but whether they should be able to open a colleague’s draft.

In practice: A six-person agency running twenty client accounts splits cleanly along those lines: two Contributors on trial, two Writers, one Editor who signs off, and one Publisher who owns the calendar.

Fits

A team where writing and publishing are done by different people.

Does not help

A two-person team where both people publish, because both would take Publisher and the distinction disappears.

PERMISSION CATALOGUE

The ten permission groups, and the ones that remove a whole area from view

RecurPost groups every permission into ten areas. The groups marked below carry a master switch in the group header.

Posts

Write and edit their posts, edit others’ posts, delete own posts, delete others’ posts. Editing others’ posts reaches any post, whoever it is assigned to, including posts already in client review or scheduled.

Approvals and publishing

Approve or reject, and publish or schedule. Publish or schedule also turns on the Share a post composer, CSV upload, and the AI tools in the sidebar, because each of those ends with a post on the schedule.

Social profiles

Add a social account, delete a social account, edit social account settings such as time zone, watermark, and posting defaults.