Who can see a voice application

Everything a person may do in Voice IntELIEgence comes from their role, and roles are edited in Access Control — not inside the application. This page names the permission behind each surface.

What you'll need

• The Voice IntELIEgence module visible in your left-hand navigation.
• These permissions: Voice · App — VIEW, Roles & Permissions · Role — UPDATE.
• Permission to edit a role in Access Control. A person's role is fixed when they are invited, so widening what they reach usually means editing the role they already hold.

If Voice IntELIEgence isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.

Steps

1. Select Access Control in the left-hand navigation, then Roles, and open the role your people hold. Each row shows its TYPE, its KEY and its PERMISSIONS count.

2. Under Permissions, type Voice into Search by feature name — it matches the row name, not the underlying key. Tick VIEW on Voice · App to make the module visible and open every voice application in it; on Voice · Conversation for conversations, transcripts, outputs and playback; on Voice · Export to fill the export jobs table; and on Voice · Audit for a conversation’s Audit tab.

3. Tick UPDATE on Voice · App for Settings, and DELETE on Voice · Conversation for deleting conversations.

4. Select Save Permissions. Reset Changes puts your ticks back as they were.

5. A role reaches a person only as they are invited, under Pre-Assign — so pre-assign the role you have just edited.

What success looks like

• Permissions saved successfully! appears, and the PERMISSIONS count on Roles matches your ticks.
• Voice IntELIEgence appears in that person’s left-hand navigation; without VIEW on Voice · App there is no entry at all.
• Their Conversations list fills with rows instead of staying empty.

Voice access is workspace-wide

VIEW on Voice · App cannot be narrowed: anyone holding it sees every voice application in the workspace, and with VIEW on Voice · Conversation every conversation inside them. Departments and groups play no part. What you can hide is a whole section — turning Topics & sentiment or Grade off in Settings removes Topics & Sentiment or Grading for everyone, and, like any settings save, pins a new version that applies to conversations started afterwards.

If something goes wrong

Symptom	Likely cause	What to do
Voice IntELIEgence is not in someone’s navigation.	Their role lacks VIEW on Voice · App — the module is hidden outright, not greyed out.	Tick it on their role and save.
A section opens but stays empty.	VIEW on Voice · App is the only permission the browser checks; the rest are enforced per request, and a refusal returns nothing rather than an error.	Tick VIEW for that surface — Voice · Conversation, Voice · Export or Voice · Audit.
Selecting the approve button — Approve & Next, or Approve when there is no next conversation — Re-run or a summary Edit does not take effect.	Those controls are shown by the conversation’s state, not by permission, so a role change will not affect them.	Check the conversation itself: an approved or still-running conversation offers them but does nothing.
The application’s Access section lists no roles.	Grants are not made there.	Edit the role in Access Control — see Roles.
A deleted conversation still answers in Chat.	Deleting warned that a copy remains in Knowledge Base or IntelieDoc, where you cannot delete.	Ask someone who can delete there to remove the copy.

Next

• Roles — the only thing that carries permissions; Departments and Groups carry none.
• Inviting a user — the one place a role reaches a person.
• Exporting voice outputs — what leaves the workspace, and who may send it.