Members & roles
Invite people to your organisation, give each a role in every project or in the projects they need, and give personal memory to whoever should have it.
An organisation's members are listed under Settings › Members in the console, with each one's access and whether they use two-factor sign-in.
On My memory too
My memory, at memory.alexein.ai, is a different product with its own organisations: the same account signs in to it, but a team here is not one there. Its My memory › Settings › Members works as this page describes, and adds each member's personal memory and seat: see Personal memory for each member below, and My memory's settings.
Roles
Owners and Admins hold their role in every project. Everyone else is a project member: a Developer or a Viewer in each project they are given, and they see no other.
| Role | What it can do |
|---|---|
| Owner | Everything in every project, including billing and deleting the organisation. |
| Admin | Every project: members, projects, keys, webhooks, connectors, budget, models and memory. |
| Developer | In its projects: keys, webhooks, connectors, the playground, app users and erasure. |
| Viewer | In its projects: reads the console. No keys, no writes, no erasure. |
In more detail:
| Can | Owner | Admin | Developer | Viewer |
|---|---|---|---|---|
| Read the console, app users and logs | ✓ | ✓ | ✓ | ✓ |
| Write memory: playground, import | ✓ | ✓ | ✓ | |
| Erase an app user's memory | ✓ | ✓ | ✓ | |
| Create and revoke API keys | ✓ | ✓ | ✓ | |
| Create, rename and delete projects | ✓ | ✓ | ||
| Set the daily budget | ✓ | ✓ | ||
| Choose the desktop app's chat models (memory platform) | ✓ | ✓ | ||
| Invite and remove members, change roles | ✓ | ✓ | ||
| Rename the organisation | ✓ | ✓ | ||
| Give personal memory and set its cap (memory platform) | ✓ | |||
| Manage billing, delete the organisation | ✓ |
Only an Owner makes Owners, and an Owner can be changed or removed only by an Owner. Nobody changes or removes themselves.
A Viewer connecting claude.ai or ChatGPT to a project's app user can grant Read only and nothing more.
Invite someone
Under Settings › Members, select Invite member (Owners and Admins).
Enter their email and choose a role. For a project member, choose Developer, Viewer or No access for each project; they need a role in at least one.
On the memory platform, an Owner can also tick Personal memory and set its Daily cap (USD), $0.50 to start.
Select Send invitation. They get an email with a link that works for 7 days. You can also copy the link and send it yourself.
The invitation is one page from the email to the platform it is for. It says who invited them, the role and projects, and, when given, that they have a personal memory of their own, which only they can read, not even the organisation's Owners, and which the Alexein desktop app uses. Someone without an account signs up on that page, with the invited email filled in, and joins once they verify it. Someone already signed in joins with one click, or selects Decline. An invited person is not asked who Alexein is for.
Pending invitations, under the members, lists the invitations still open, each with a link to copy and Cancel.
Personal memory for each member
Personal memory is a member's own memory: their connectors feed it, and the desktop app and the assistants they connect to it use it. Nobody else can read it, Owners included. It is on the memory platform only, so all of this is under My memory › Settings › Members.
- Who has it. Whoever creates the organisation has it from the start, on the organisation's free seat for its first month. An Owner or Admin gives it to anyone else, in the invite or with Personal on their row, themselves included.
- Its seat. Personal memory is sold as seats, bought under My memory › Billing. Turned on, it takes a free seat. A member whose personal memory is on without one shows Needs a seat, and Assign a seat gives them one when one is free; until then their memory is refused, and kept.
- Who sees it. The Personal memory column shows On with its daily cap, or Off. Owners and Admins see it for everyone; anyone else sees only their own.
- Its cap. An Owner sets each member's daily cap under My memory › Settings › Limits, from more than $0 up to $100. Its spend does not count against the organisation's daily budget, and chat in the desktop app uses the seat's credits instead.
- Turning it off. An Owner unticks it with Personal. The member's keys, connectors and connected apps stop at once. Its memory is erased in 30 days unless it is turned on again.
Change or remove a member
Edit access changes a member's role or projects. A connection to an app user that their new role no longer allows, such as a Read and save connection after they became a Viewer, has to sign in again.
Remove takes away their access to the organisation at once. Keys they created for a project keep working until revoked, under API keys. Their personal memory is turned off as above: kept 30 days, then erased.
Related
- Personal memory
- Limits: the daily budget and every cap.
- Authentication & keys: projects and their keys.