Members, groups and roles
Admin → Members
| Role | Can | Why you would use it |
|---|---|---|
member |
Use Lucy within the organisation’s settings | Everyone |
org_admin |
Everything a member can, plus all Organisation settings | Keep this to a few named people |
auditor |
Read the audit log and nothing else | Compliance, internal audit, DPO. They see no conversations and change nothing |
Separation of duties. Give your compliance or risk function the auditor role. They can verify what admins do without being
able to change it.
Groups
Section titled “Groups”Groups come from your identity provider, so access follows your directory. You can use them to:
- set limits per group,
- grant web search, agents or specific models to a group,
- scope shared memory.
Granting to a group is the recommended way to run a pilot: add the pilot group, and later widen it, without touching individuals.
Member detail page
Section titled “Member detail page”Each member has a page with their connections (which connectors they linked) and recent activity. Use it to answer “who connected what” during a review. You can see that a connection exists; you cannot see anyone’s tokens.
Removing someone
Section titled “Removing someone”Remove… on the member page, typically when someone leaves.
Deleted: their conversations, files, sandboxes, memory, devices, preferences and usage counters, their connector connections, and their name and email. Their access is revoked.
Kept: the audit log and the cost ledger. These are your record of what happened and what was spent.
This supports a GDPR erasure request and a clean leaver process in one action, and leaves your accountability trail intact.
Examples
Section titled “Examples”Separation of duties for audit
Section titled “Separation of duties for audit”Situation: Internal audit wants to check what admins do, without being able to change it.
Setup: Give the audit lead the auditor role. Keep org_admin to two named people.
Result: The auditor sees the audit log and nothing else. A change you make leaves a record they can read.
A leaver on a Friday
Section titled “A leaver on a Friday”Situation: An analyst resigns. HR closes their account at 17:00. Setup: Disable them at your identity provider (sign-in stops), then Remove them in Lucy to delete their conversations, files, sandboxes and memory. Result: Their data is gone, their connector tokens are deleted, and the audit trail remains. Their agents stop.
A pilot group
Section titled “A pilot group”Situation: You want 15 people from compliance to try Lucy before anyone else. Setup: Use a group from your identity provider, and grant web search, models and agents to that group only. Result: Widening the pilot later is one group at a time, not setting by setting.