Skip to main content
Each Registry schema has its own settings panel where you can update its name, icon, color, and description, and control who can access it. Open a schema and click the Settings tab to access these options.

​
Schema details

Click Save after changing any detail field.

​
Schema permissions

Access to a schema is controlled by role assignments — you decide who can see it and what they can do. This is separate from the space-level Permission Scheme; Registry is an instance-wide module.

​
Schema roles

Users with a Registry Admin module role (granted in Admin → Roles & App Access) can access all schemas regardless of per-schema assignments.

​
Managing schema permissions

1

Open the schema and go to Settings → Permissions

The Permissions tab shows all current user and group assignments.
2

Add a user or group

Click Add Access, search for the user or group, and select a role.
3

Save

Access is granted immediately. Users see the schema in their Registry sidebar.
To remove access, click the remove icon on the user’s or group’s row. They immediately lose access to the schema and all its objects.

​
Default role

You can set a Default role for the schema. Any user with the Registry User module access who is not explicitly assigned a role receives this default role when they open the schema.

​
Renaming a schema

1

Open the settings tab

Open the schema and click the Settings tab.
2

Edit the name

Edit the Name field.
3

Save

Click Save.
The new name appears in the Registry sidebar and throughout the UI immediately.

​
Changing the icon or color

1

Open the schema settings

Open the schema settings.
2

Choose an icon

Click the Icon field to open the icon picker and select a new icon.
3

Choose a color

Click the Color field to choose a new accent color.
4

Save

Click Save.

​
Schema ownership

The user who created a schema is its owner. There is currently no way to transfer ownership of a schema to another user.
Registry is not scoped to a Space. Space admins have no special access to Registry schemas — access is controlled exclusively through the schema’s Settings → Permissions tab and the module access role granted in Admin → Roles & App Access.

​
Deleting a schema

Deleting a schema permanently and irreversibly removes all object types, all attribute definitions, all objects, all field values, and all relations within the schema. This cannot be undone. Export any important data before proceeding.
1

Open Schema Settings

Open the schema you want to delete and click the Settings tab.
2

Scroll to the Danger Zone

Scroll to the bottom of the settings page to find the Danger Zone section.
3

Click Delete Schema

Click Delete Schema. A confirmation dialog appears.
4

Confirm by typing the schema name

Type the exact schema name in the confirmation field to confirm you intend to delete it, then click Delete.
After deletion, the schema no longer appears in the Registry sidebar. Any project tasks that had a Registry Object field pointing to objects in this schema will show an empty value for that field.

​
Next steps

Importing Objects from CSV

Bulk-create registry objects by uploading a CSV file.

Registry

The Registry is Collabase’s built-in structured data store.
Last modified on October 13, 2026