Permissions & Access

Eric permissions are controlled by a mix of role, feature toggles, dataset permissions, and environment rules.

Access matrix

Capability	Who can do it	Extra requirements
Open Eric chat	Admin, Staff, Member	Staff and Members need AI Chat Access enabled.
Open full AI Assistant settings	Admin / Giga Admin	Admin or Giga Admin role required for billing and capacity management.
View chat-side usage and credits	Admin, Staff, Member	Requires AI Chat Access. Read-only for non-admins.
Open Company Knowledge	Admin, Staff, Member, permissioned users	Requires AI Chat Access or Company Knowledge Update Permission.
Browse Company Knowledge content	Admitted workspace users	Each directory and file follows personal, Dataset, Dashboard, and company permissions.
Inspect Definition Files	Admitted workspace users	Visible YAML is read-only here and follows access to its owning product object.
Edit Dataset Knowledge	Admin, Staff, Member	Requires Dataset access and Dataset Knowledge Contribution Permission.
Edit Company Knowledge	Permissioned users	Requires Company Knowledge Update Permission.
Approve Knowledge Proposals	Permissioned users	Requires Company Knowledge Update Permission.
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

AI access is governed by permissions and the active OEM capability policy, not a beta flag.

On Liongard (OEM_ID=liongard), the Eric main chat surface stays available to Users with AI Chat Access; AI Assistant settings and Company Knowledge workspace routes are excluded by the OEM pack.
In all other deployments, access depends on the user’s role and feature toggles.
Giga Admin users can work with AI tooling across companies 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

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

Company-wide knowledge edits and proposal approvals are gated by Company Knowledge Update Permission. Dataset knowledge edits use a separate Dataset Knowledge Contribution Permission and still require access to the underlying Dataset.

How dataset permissions affect Eric

Eric always respects dataset permissions.

Key rules

If a user cannot access a dataset in Resplendent, Eric cannot use it for that user
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

These are the practical defaults in the current UI:

Role	Eric chat by default	Company Knowledge updates
Admin	Yes	When permission is enabled
Staff	No, enable AI Chat Access if needed	When permission is enabled
Member	No, enable AI Chat Access if needed	When permission is enabled

Users admitted to Company Knowledge can edit Knowledge Files in their own Personal Knowledge Directory. The unified Map and Files views omit inaccessible roots, files, and generated entries rather than showing locked placeholders.

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.