Projects & team

A project is a workspace: it holds its own blueprints, content, workflows, API tokens and members. Nothing is shared between projects: an API token only ever reaches the project it was created in.

Creating a project

Any signed-in user can create a project, from the Projects page (New Project) or from the project switcher (New project). A project only needs a name.

You become the project's Administrator and land on its dashboard. The project's URL slug is derived from the name when it is created; renaming the project later does not change it.

Switching projects

The project switcher sits at the top of the sidebar and lists every project you are a member of. Pick one to open it, or choose All projects to open the Projects page, which shows them as cards with their number of blueprints and resources.

Groups

On the Projects page, sort projects into groups from a card's menu: Move to group, New group… or Remove from group. Once a group exists, tabs at the top filter the list by group.

A group is stored on the project itself, so every member of the project sees the same grouping.

Project settings

Open Project settings from the user menu at the bottom of the sidebar. Only Administrators can access it.

Setting	Description
Project name	Shown in the switcher and across the dashboard.
Domains	The domains where your content is published, for reference. Use Add domain to add one.

Click Save changes to apply.

Deleting a project

Under Danger zone, click Delete project and type permanently delete to confirm. The project immediately disappears for every member, along with its blueprints, content and settings.

WARNING

Deleting a project also stops every API token issued for it. Make sure no live site still depends on it.

Members

The Users page (sidebar, under Configuration) lists the project's members with their email and role. Only Administrators can manage members.

Adding a member

Click Add a user, enter the person's email and choose a role, then Add user.

The person must already have a Diggama account: members are added by the email of an existing account, and no invitation email is sent. Ask them to sign up first if they have not.

Changing a role or removing a member

Each row has Change role and Remove. Removing a member revokes their access to the project; you can add them back at any time.

Two guard rails apply:

• You cannot change your own role or remove yourself: your own row has no actions.
• A project always keeps at least one Administrator: the last one cannot be demoted or removed.

Roles

Roles are cumulative: a Developer can do everything an Editor can, and an Administrator everything a Developer can.

	Editor	Developer	Administrator
Browse content	✓	✓	✓
Create, edit and delete resources	✓	✓	✓
Publish and unpublish resources	✓	✓	✓
Upload images to the media library	✓	✓	✓
Create and edit blueprints and their fields		✓	✓
Manage workflows		✓	✓
Manage API tokens and Connect to AI		✓	✓
Manage members (Users)			✓
Rename or delete the project (Project settings)			✓

TIP

Give content editors the Editor role. It covers the whole editorial loop (writing, editing and publishing) without letting anyone change the structure your front end relies on.