Groups & permissions

Groups are how Insight AI models your team. They serve three purposes:

• Ownership — every data source belongs to a group, and that group’s key encrypts the source’s stored credentials.
• Structure — groups nest into a parent/child hierarchy that can mirror your org chart (e.g. Company → Finance → Accounts_Payable).
• Permission levels — each group carries a level describing its intended access: Viewer (view content), Editor (view and contribute), or None.

Find groups under the Users tab in the dashboard, shown as an expandable tree.

Note

Badges on existing groups display the permission’s internal value — read (Viewer), write (Editor), or none.

Create a group

1. Select Create Group.
2. Enter a Group Name — at least 2 characters, no spaces (use underscores, e.g. data_team).
3. Choose a Permission Level (Viewer, Editor, or None).
4. Optionally pick a Parent Group — leave it empty to create a root-level group.
5. Select Create Group.

To add a subgroup directly under an existing group, open that group’s action menu and choose Add Subgroup — the parent is pre-selected.

Edit a group

Open a group’s action menu and choose edit to change its name, permission level, or parent. Moves that would create a loop in the hierarchy (making a group its own ancestor) are rejected.

Manage members

Open a group and switch to the Members tab.

• Add one member: select +, enter the person’s email address (or user ID), and select Add Member. The person must already have an Insight AI account.
• Add several at once: switch the dialog to Add Batch, paste emails separated by commas or spaces, select Add to Stack to turn them into a reviewable list, then Process & Add Members.
• Remove a member: select the trash icon next to them and confirm.

Note

A user can belong to only one group at a time. Adding someone who is already in another group will fail — remove them from the old group first.

The hierarchy

The Subgroups tab of any group lists its children, and the tree view on the Users page shows the whole structure at once. Deleting a group does not delete its subgroups — they become root-level groups instead.

Practical tips

• Create at least one group before connecting data sources — the source creation form requires an Owner Group.
• Keep group names short and descriptive; they appear in dropdowns when creating data sources.
• Deleting a group whose key protects data-source credentials makes those sources unusable — delete or migrate the sources first.