Skip to content

How-to guide

Set up team governance

This tutorial walks you through configuring governance in your workspace: roles, approvals, and classifications. In a few steps, you will establish a control framework over…

2 min

Goal: verify that a reader can inspect authorized data and that unauthorized writing is refused. Use a test workspace with at least two members and an administrator able to manage permissions.

1. Assign responsibilities

Assign roles through member settings. Choose a reader and an editor. Record effective permissions; a role name alone does not describe every applicable rule.

Use workspaces and explicitly authorized access to separate organizations. A space named Customer A organizes a canvas without establishing this boundary. See Workspaces and spaces.

2. Prepare a sample

Use Client and CLI-001. Record its identifier, values and workspace. Confirm that the editor can locate it. Prepare a reversible change to test data, such as its display label, and retain the initial value.

3. Test reading and writing

Sign in as the reader. Inspect the sample and verify that writing is unavailable or refused. A hidden button alone does not prove server enforcement: for integrations, separately test a published operation using the applicable key and permissions.

As the editor, verify only the authorized change on demonstration data. Reopen the record, inspect the result and restore the initial value.

IdentityCheckExpected result
ReaderRead within scopeAccessible record
ReaderWrite without permissionRefusal or unavailable operation
EditorAuthorized changeSaved and reread value
External keyPublished operation with its scopesResult consistent with its own permissions

4. Check additional controls

If classifications or approvals are enabled, inspect configuration and test the operation they should protect. A descriptive classification does not grant permission. A saved policy does not establish that every write path requires approval.

Retain evidence of the request, its state and the verified outcome. Use The controlled-action journey for preparation.

Expected result

You have a permission matrix tested with actual identities, including a refused case. Record unavailable controls and repeat tests after role, source or API changes. See Roles and permissions.

Did this page help you achieve your goal?