What are Roles?

A Role decides what someone can do once they are in Splinde: whether they can change workspace-wide settings, and which budgets they can see at all. Splinde runs two separate role systems side by side, one for the Workspace and one for each Project, and they answer two different questions.

What it's for

A team needs some way to say who runs the workspace and who can look at a given client's budgets. Roles keep those two decisions apart: workspace roles govern administration, Project roles govern visibility. A person's workspace role and their Project roles are independent, so an Editor can be the Owner of a Project, and an Admin sees a Project only once they are one of its members.

How it works

Workspace roles

A Workspace has two roles, Editor and Admin. Both create and edit budgets, create a Project, and see the member list. Admins also invite people, change someone's role, remove a member, and delete a budget that is not filed under a Project. Only Admins see the Plan & billing panel in Settings, and workspace-wide settings such as Labels and Units are managed by Admins too.

Settings, Team, also holds a Downgrade to Member menu item on another member's row. It sets that person's role to Editor, and their Role column reads Editor afterward.

A budget that is not filed under any Project follows the workspace role: every workspace member can open and edit it, Editor or Admin.

Project roles

A Project has two roles of its own, Owner and Member. Project membership is what decides who can see the budgets inside that Project. A budget filed under a Project is visible to that Project's members, Owners and Members alike, whatever their workspace role. Owners also add or remove Project people and delete the Project.

This is what lets you decide exactly who sees a client's work: invite someone to one Project and that is the only one they see.

Access to any single budget always comes from one of these two paths, workspace membership or Project membership, rather than a role assigned to the budget itself.

Good to know

Admin-only controls, such as Invite new Member or a member's row menu, are visible to Editors too. They are there for Admins to use, and an Editor who needs one done can ask an Admin.

Related

• I'm adding people to the workspace. Who should be an Editor and who an Admin?

• How do I make sure freelancers only see their own project?

• What is a Workspace?

• What is a Project?