PegacraftProjects and roles
Running more than one brand from one login, and what each role can do.
Pegacraft is multi-project: one login can hold a separate membership in more than one project (internally, a tenant), each with its own channels, content, brand voice, and knowledge base, fully isolated from every other project. This is what lets one operator run several brands without juggling separate logins.
Switching projects
The sidebar shows your current project as a small dropdown, right below the Pegacraft mark. Click it to see every project you belong to and switch between them, or create a new one with + New project. Switching re-scopes the whole console: channels, content, replies, and analytics all become that project's data.
Creating a project makes you its owner immediately. There's no approval step: Pegacraft is a self-hosted internal tool for a small team, not a gated multi-tenant product, so any logged-in operator can start a new project.
Roles
Each membership in a project carries one role. A person can be Owner of one project and Creator on another. Roles matter for one thing: whether an action is allowed on the project you're currently switched into.
| Role | Can do |
|---|---|
| Owner | Everything, including adding/removing channels and changing guardrail settings. |
| Manager | Add/edit channels, configs, and reply guardrails. Cannot remove channels. |
| Creator | Read everything; create and edit content, but can't touch channels, configs, or guardrails. |
| Moderator | Read everything; can approve, dismiss, or send a reply in Reply Manage, but can't change what it's configured to do. |
A role that can't perform an action gets a plain rejection when it tries, not a hidden button: the console doesn't try to guess what you meant to click, it tells you the action needs a different role.