Users & Roles

Manage your team

Svalla has a built-in user management system for your back-office team. Administrators can:

• Invite users — send email invitations to new team members
• Assign roles — set permissions at system, project, and post type levels
• Manage profiles — users have profiles with name, email, photo, and bio
• Block/unblock — temporarily suspend user access without deleting the account
• Track activity — see when users last logged in and what changes they made

Global access levels

System roles define a user's overall access to the Svalla installation:

• Super — full system access, can manage all projects and system settings
• Developer — technical access to all projects, API configurations, and developer tools
• Administrator — can manage projects they're assigned to
• User — standard user, permissions defined at project level

System roles set the ceiling for what a user can do. Project and post type roles further refine access within specific projects.

Per-project permissions

Within each project, users are assigned a project role that controls their access:

• Administrator — full control over the project: settings, templates, sections, users, and all content
• Manager — can manage content, categories, and forms, but cannot change project settings or user permissions
• Editor — can create, edit, and publish content. Can approve or reject drafts from contributors
• Contributor — can create and edit content, but can only save as draft. Cannot publish directly

A user can have different roles in different projects. For example, an editor in one project might be a contributor in another.

Fine-grained content access

For even more precise control, you can set permissions at the post type level:

• Administrator — full access to this post type and its content
• Editor — can create, edit, and publish posts in this type
• Viewer — can view but not edit content in this post type
• Blocked — no access to this post type at all

This is useful when different team members are responsible for different types of content. For example, the marketing team edits blog articles while only project managers can edit service pages.

One account, multiple projects

A single user account can have access to multiple projects with different roles in each. This is managed from the project settings:

• Add users to a project and assign their role
• Remove users from a project to revoke access
• Change roles as team responsibilities evolve

Users see only the projects they have access to in their dashboard. This keeps the interface clean and prevents unauthorized access to other projects.