Sharing & Access Control¶
Share your assistant like a document: every project has a permanent URL, and you decide who can use it.
Roles¶
| Role | Capabilities |
|---|---|
| Owner | Full control, including deleting the project. |
| Admin | Manage documents, settings, exports, and API keys — everything except deletion. |
| Regular user | Chat with the assistant. |
Owners and admins are also the only ones who can access sensitive data such as conversation-history exports and API keys.
Granting access¶
Email invitations¶
Invite individual users by email address and assign them a role.
Approved email list¶
Maintain a list of addresses allowed to use the project. You can approve:
- Individual addresses —
student@illinois.edu - Entire domains —
@illinois.eduadmits anyone with an Illinois email
Public vs. private¶
- Private (default) — only approved users can access the project.
- Public — anyone with the URL can chat, no login required.
Public projects expose your documents indirectly
A public assistant will answer questions using your uploaded materials and cite passages from them. Don't make a project public if its documents shouldn't be visible to the world.
Analytics on shared projects¶
Once shared, the Analysis page shows how users interact with your assistant — see Analytics.