Sosyabot Docs

English

Türkçe

English

Türkçe

Appearance

Roles & permissions ​

A role is a label you give each teammate that decides what they can do in your workspace.

Why it matters ​

Roles keep your workspace tidy and safe. You give people just enough access to do their job, and nothing more, so no one changes billing or settings by accident.

Step by step ​

Open your team list

Go to your workspace and open the list of people on your team. You will see each person's name and their current role.

Pick the right role for each person

Click the role next to a person and choose one:

  • Owner can do everything, including billing and deleting the workspace.
  • Admin can change settings and manage people, but not billing.
  • Editor can create, schedule, and publish posts.
  • Viewer can look at things only, with no changes allowed.

Save and you're done

Your choice takes effect right away. The person sees their new access the next time they open Sosyabot.

TIP

When in doubt, start someone low (like Viewer or Editor) and raise their role later. It is easier to give more access than to undo a mistake.

Good to know ​

  • Only an Owner can make someone else an Owner, or remove an Owner.
  • Admins can change anyone's role except the Owner.
  • Billing is reserved for Owners only, so the wrong person cannot change your plan.
  • A new teammate you invite usually starts with a basic role, and you can raise it whenever you like.

Workspace

Invitations

Plans

For developers

Roles live on the workspace_member record and are enforced at the API layer. Five roles exist, ranked by ROLE_RANK:

  • owner (5) — everything in admin plus billing changes and workspace deletion.
  • admin (4) — manage members, channels, integrations; configure workspace; not billing.
  • editor (3) — create, schedule, publish posts; manage labels and campaigns.
  • author (2) — create drafts and submit for review. Default invitation role.
  • viewer (1) — read-only.

"At least admin" gates check rank >= 4. Change a role with PATCH /api/v1/workspace/members/:id and a body of { role: "editor" }. Only owners can promote to or demote from owner; admins can change any role below owner. The separate admin permission on the user record grants instance-level admin panel access — see Admin Overview.