Roles, Permissions and the Activity Log: How Access Control Works in SchedulifyX

SchedulifyX Team · May 12, 2026

What the permission system actually contains - real roles, around sixty-five permission keys, and a full activity log.

The roles that exist

The roles that exist
The roles that exist

A brand has an owner, and members joined as admins, managers or members. Each role maps to a set of permission keys - around sixty-five of them - covering posts, approvals, accounts, analytics, integrations and team management. A manager can be allowed to schedule but not to connect accounts; a member can draft without publishing.

Approvals as a permission boundary

Approvals as a permission boundary
Approvals as a permission boundary

The approval workflow is where permissions earn their keep: drafts from contributors sit in a queue until someone with approval rights signs them off, and clients can review from a portal link without receiving a login to the workspace at all.

The activity log

The activity log
The activity log

Every meaningful action - publishing, edits, approvals, connection changes, permission changes - lands in the activity log with who, what and when. When two people disagree about what happened to a post, the log answers it.

What we do not claim

Two things you will not find here, said plainly because vendors often imply otherwise: there is no SAML or IdP-managed single sign-on, and we hold no compliance certifications to advertise. If those are hard requirements for your organisation, we would rather you know before you evaluate than after.

You can try everything described here on the free plan - create an account and it is all in the left-hand menu.

SchedulifyX