Permissions & Access
Eric permissions are controlled by a mix of role, feature toggles, dataset permissions, and environment rules.
Access matrix
Section titled “Access matrix”| Capability | Who can do it | Extra requirements |
|---|---|---|
| Open Eric chat | Admin, Staff, Member | Staff and Members need AI Chat Access enabled. |
| Open AI Assistant settings | Admin / Giga Admin | Admin or Giga Admin role required. |
| Use dataset context updates | Staff / Admin / Giga Admin | AI Context Updates must be enabled, and onboarding must already be complete. |
| Open Run Inspector | Admin / Giga Admin | Available from assistant messages that have a run attached. |
| Open Trace Viewer | Admin / Giga Admin | Available from the Eric sidebar or direct trace URL. |
Environment and company availability
Section titled “Environment and company availability”AI access is governed by permissions, not a beta flag.
- In Liongard environments, the Eric header icon, sidebar, and
/ericpage are hidden for everyone. - In all other environments, access depends on the user’s role and feature toggles.
- Giga Admin users can work with AI tooling across company contexts where applicable.
If a user does not have the AI Chat Access feature permission, they cannot open /eric even if their role would otherwise allow it.
Feature toggles that affect Eric
Section titled “Feature toggles that affect Eric”AI Chat Access
Section titled “AI Chat Access”This toggle controls who can open Eric.
- Admins can access Eric by default
- Staff do not get Eric by default; enable AI Chat Access if they should use chat
- Members only see this Eric-specific toggle in the user edit page
AI Context Updates
Section titled “AI Context Updates”This toggle is separate from chat access.
It is designed for people who maintain data definitions, especially staff and admins working in:
- Datasets
- Modified Datasets
- Joined Datasets
Dataset context updates require:
- Onboarding must already be complete before the prompt can open
- The user must have the AI Context Updates feature permission
How dataset permissions affect Eric
Section titled “How dataset permissions affect Eric”Eric always respects dataset permissions.
Key rules
Section titled “Key rules”- If a user cannot access a dataset in Resplendent, Eric cannot use it for that user
- Pinned context and
@mentions only show items the current user can access - Dataset whitelist and blacklist rules apply inside chat
- Member dataset access inside Eric is always Read Only
- Giving a member AI Chat Access does not grant access to the raw Datasets or Modified Datasets pages
Role defaults
Section titled “Role defaults”These are the practical defaults in the current UI:
| Role | Eric chat by default | AI context updates by default |
|---|---|---|
| Admin | Yes | Yes |
| Staff | No, enable AI Chat Access if needed | Yes |
| Member | No, enable AI Chat Access if needed | Not available |
Admin-only diagnostics
Section titled “Admin-only diagnostics”Two Eric debugging tools are intentionally admin-only:
- Run Inspector inside chat
- Trace Viewer for session-level debugging
This keeps everyday users focused on answers while giving admins the tools needed to troubleshoot behavior.