Team roles and permissions

Styrar company workspaces use roles and capabilities so owners can delegate work without giving everyone full admin access. This keeps publishing, billing, integrations, brand access, and team management under control as the workspace grows.

Think of roles as named bundles of permissions. Capabilities are the individual actions inside those bundles, such as creating posts, managing billing, inviting members, or editing automations. Owners and admins can use built-in roles for simple teams or custom roles for more specific access patterns.

Members and roles

Invite people to your company from Settings → Workspace. Each member has a role, such as owner, admin, member, or viewer, plus any custom roles your company defines. Roles control what they can see and change.

Use the least access that lets someone do their job:

• Owners manage the workspace, billing, membership, and high-risk settings.
• Admins help operate the workspace and manage team workflows.
• Members usually create and manage content.
• Viewers can review work without changing important settings.
• Custom roles can match agency, client, contractor, or approval-only responsibilities.

Before inviting external collaborators, decide whether they need full workspace access or only a narrower role. Remove members promptly when they no longer work on the account.

Capabilities

Fine-grained permissions map to what each role can do: creating posts, managing billing, editing automations, viewing analytics, managing company settings, and more. Owners and admins typically manage membership and roles.

Capabilities matter because Styrar has many connected areas. A person who writes captions may not need billing access. A finance user may need invoices but not social publishing. A developer may need API keys but not approval authority. Separating these responsibilities reduces risk and makes audits easier.

If someone cannot see a page or complete an action, check their role first. The navigation may hide areas that do not apply to their permissions or the active workspace.

Brands

Companies can have multiple brands. Non-owner/admin members may be limited to specific brands via brand access, while Social accounts stay shared at the company level unless your workflow says otherwise. Brand access helps agencies and multi-brand teams keep content responsibilities clear.

Use brand access when:

• A teammate works on one client but not another.
• A contractor should only see assigned brand work.
• An approver is responsible for a specific product line.
• You want campaign organization without creating separate companies.

Owners and admins should review brand access whenever a new brand is added. Otherwise, members may not see the work they need, or they may see more than intended.

Switching context

Use the workspace switcher to move between personal and company contexts. Available nav items, for example Approval flows, may depend on whether a company is active. Personal work and company work can have different limits, roles, billing, brands, and connected resources.

If something looks missing, first check the active workspace. Many support requests come from users editing personal scope when they meant to work in a company, or the reverse.

Approval and publishing control

Roles work together with approval flows. A member may be allowed to create drafts but still need approval before publishing. An approver may be able to review and approve posts without managing billing or integrations. This lets teams move quickly while keeping final control with the right people.

For sensitive brands, use approvals for public posts, restrict billing and API access to trusted admins, and review member access regularly.

Recommended maintenance

• Review members monthly for active company workspaces.
• Remove users who no longer need access.
• Keep owner count small but not dependent on one person.
• Use custom roles only when built-in roles are too broad.
• Document who owns billing, publishing, approvals, and integrations.
• Check brand access after adding new brands or clients.

Good permission hygiene prevents accidents. It also makes onboarding easier because each person gets a role that matches their actual responsibilities.

Need more help?

Open a ticket from Help → Tickets (sign in required).