Access Controls and Auditability

The roles Tenali has, what each one can reach, and which privileged actions are recorded.

Roles

Tenali has two roles you assign:

User — sees their own meetings, recordings, transcripts and sources, plus anything shared with the whole workspace.
Admin — everything a User can do, plus team management, billing, organization sources, and organization-wide question analytics.

Roles are set inside Tenali by an admin. They are permanent settings on a member's record until an admin changes them.

Admins Can Reach Team Meetings

This is the part most worth understanding before rollout: Admins can see and open other members' meetings, including summaries and transcripts, and can export them. The Admin Full Access setting extends what admins can do further — organization-wide chat, edits on team meetings, and re-signed recording playback.

For exactly which capability sits behind which gate, see All Team Meetings and Roles and Permissions. If your team should know their calls are visible to admins, tell them during rollout rather than after.

What Gets Logged

Tenali records privileged actions taken against another member's data, including:

an admin viewing a member's meeting list or opening one of their meetings
admin edits to a team meeting
deletions
PDF exports and shares of a team member's meeting
recording playback

These logs are internal — there is no customer-readable audit log or export in the product today. If you need audit evidence for a review, request it from security@tenali.ai.

Practical Guidance

Keep the number of admins small, since Admin carries visibility over team meetings.
Add Tenali to your offboarding checklist — IdP removal doesn't propagate.
Review who holds Admin on a cadence that suits your policy; Tenali won't prompt you.