Appearance
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 and account block at the bottom of the sidebar (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 block at the bottom of the sidebar shows the project you are in and who you are. Click it to list every project you are a member of (with a search box once you have more than eight). 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 Settings › General. 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.
Settings
Everything that configures a project, rather than fills it, lives under Settings: the link at the bottom of the sidebar, or the project and account block below it. Each member sees the pages their role allows:
| Page | Role |
|---|---|
| General, Edit layout, Users | Administrator |
| Blueprints, Marketplace, Workflows, Connect to AI, API Tokens | Developer and above |
Editors have no Settings pages: their sidebar holds the content and nothing else.
Edit layout
Settings › Edit layout dresses the dashboard in your brand, for every member of the project. Only Administrators can change it.
| Setting | What it does |
|---|---|
| Logo | Replaces the Diggama logo at the top of the sidebar and marks the project in the project menu. PNG, JPEG, WebP, GIF or SVG, up to 2 MB. Images are resized to 512 px wide; SVGs are cleaned of scripts and external references. |
| Brand colour | Replaces Diggama's blue everywhere: buttons, links, selection, the active page. Pick a preset, use the colour picker or type a hex code; lighter and darker shades are derived from it. A warning appears when white text on the colour would be hard to read. |
| Sidebar | Reorder content types by dragging them, sort them into named groups (up to 20), hide the ones your editors do not need, and show or hide the Dashboard. |
A preview beside the form shows the result as you edit; Save layout applies it for everyone. Reset to Diggama defaults puts back the original logo, colour and sidebar.
Hidden content types are only hidden from the sidebar: they still exist, their API still answers, and they stay reachable from Settings › Blueprints. A content type created after the layout was saved appears at the end of the sidebar, so a new blueprint is never lost.
Members
The Users page (Settings › Users) 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 (Settings › General) | ✓ | ||
| Change the logo, colour and sidebar (Settings › Edit layout) | ✓ |
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.