Overview
Persona Verify for Slack adds an identity check to sensitive requests that arrive in Slack. Before you reset a password, approve privileged access, or change an authentication policy for a coworker, you can ask that coworker to verify their identity with Persona.
Persona Verify for Slack is currently in a pilot. To request access, reach out to your Persona account team.
The person who asks for the check is the requester. The person who verifies is the recipient. The requester sends a request from Slack. The recipient gets a direct message (DM) from the Persona Verify app. The recipient can start the verification, or report that they did not make the request. When the verification ends, the requester gets the result in a DM.
The verification itself runs in Persona, with an inquiry template that your organization selects. Documents, selfies, and check results stay in Persona. Slack gets only a short status message.
A verified identity does not approve the request. “Completed” tells you that the recipient finished the Persona verification. You must still decide whether to do the action, with your usual approval process. An expired request is never an approval.
Use cases
Use Persona Verify for Slack when a request is sensitive and you want to know that the person who asks is the real coworker. For example:
- A coworker asks the IT help desk to reset a password or an MFA factor.
- A coworker asks for privileged access, or for a change to an authentication policy.
- A coworker sends an urgent request that seems unusual, such as a payment or a code-review approval.
Before you start
You need all of these:
- Access to the feature. Persona Verify for Slack is in a limited pilot. Persona must turn it on for your organization.
- A Persona inquiry template for the verification. The Slack integration page lists the inquiry templates in your active environment. Use a published template, for example a Government ID and Selfie template. Optionally, add a string field with the key
requester_name. Persona Verify for Slack puts the Slack name of the requester in this field. - A Persona Dashboard user to do the installation. This user needs these permissions in Persona:
inquiry_template:read,inquiry:read,inquiry.create:write,webhook:read, andwebhook:write. The webhook permissions are necessary for result notifications in Slack. - Permission to install apps in your Slack workspace. Your Slack workspace settings can require a Slack admin to approve the app.
- A Persona Dashboard user for each requester. Each requester connects their own Persona account to Slack. To send requests, a requester needs the Inquiry create and resume permissions for the selected inquiry template. Recipients do not need a Persona account.
Set up Persona Verify for Slack
Install the app
- In the Persona Dashboard, go to Integrations and open the Slack integration page.
- Find the Persona Verify for Slack section at the bottom of the page.
- In Inquiry template for Slack verification, select the inquiry template to use.
- Click Install Persona Verify. A new browser tab opens. If the tab does not open, allow pop-ups for the Persona Dashboard and try again.
- On the first Persona authorization page, click Authorize Persona Verify for Slack. This lets the app create inquiries with the selected template.
- On the second Persona authorization page, click Authorize Persona Verify for Slack. This lets the app set up the webhook that sends results back to Slack.
- On the Slack authorization page, select your Slack workspace and approve the request. Slack then sends you back to the Persona Dashboard.
- Make sure that the status of the Persona Verify for Slack section is Connected.
You connect one Slack workspace to one Persona environment. The app uses the inquiry template that you selected during installation. To use a different workspace or template, reconnect the app.
Check the connection status
The Persona Verify for Slack section shows one of these statuses:
| Status | What it means |
|---|---|
| Not installed | No Slack workspace is connected to this environment. |
| Connected | The app is installed and can send verification requests. |
| Reconnect required | The access of the app was removed. |
| Status unavailable | The Dashboard could not get the status. Reload the page. |
If the status is Connected but the section shows Notifications are off or Notifications stopped, the second Persona authorization did not complete or was removed. Verification requests still work, but requesters do not get results in Slack. Click Reconnect Persona Verify to fix it.
Reconnect the app
Click Reconnect Persona Verify and do the installation steps again. You must reconnect when the status is Reconnect required, when notifications are off, or when you want to change the workspace or the inquiry template. If the reconnection fails or you cancel it, the current installation does not change.
Remove the app
To stop all verification requests from a workspace, remove the Persona Verify app from your Slack workspace in the Slack app management settings. Then the Dashboard shows Reconnect required, and requesters cannot send new requests.
Send a verification request
You can send a request with a slash command or from the app’s Home tab in Slack. The two slash commands, /persona and /idv, do the same thing.
- In any Slack conversation, type
/persona @coworkerand then the reason for the request. For example:/persona @alex Please confirm your password reset request. - Send the command. The reason is optional, but it helps the recipient know which request this is.
- The first time that you send a request, Slack shows a Connect your Persona account button. Click it, sign in to Persona, and authorize the app. Your request then continues automatically.
- Slack shows you the message
@coworker was asked to verify with Persona.
To send a request without a command, open the Persona Verify app in Slack, go to the Home tab, and click Send a verification. Select the recipient, add an optional reason, and submit the form. With this method, the app sends all replies to you as DMs.
Other commands:
/persona helpshows how to use the command./persona disconnectremoves your Persona connection from Slack. You can also do this in Home > Settings. The next request asks you to connect again.
You cannot send a request to yourself. Each request creates one inquiry in Persona with your own Persona account, so Persona applies your permissions.
Shared group DM
In Home > Settings, a requester can turn on Start a direct message when a request is sent. Then each request also opens a group DM between the requester, the recipient, and the app. The group DM shows the request and its status. It never contains the verification link. This option is available only when the Slack workspace allowed the optional group DM permission during installation.
Respond to a verification request
The recipient gets a DM from the Persona Verify app with the title Identity verification request. It names the requester, shows the reason, and tells the recipient when the request expires.
- To verify, click Start verification. The verification opens in your browser. Follow the steps, for example take a photo of your government ID and a selfie.
- If you did not make this request, click Report this request and confirm. The app tells the requester that you reported the request, and removes the verification link from your DM.
Only the recipient can report a request. Report a request when somebody asked for a sensitive change in your name, and you did not ask for it. This is a sign that somebody tries to impersonate you.
When you report a request, the app removes the link from Slack, but Persona does not cancel the inquiry. The link stays valid until it expires.
The link is a one-time link. Do not share it. The DM tells you how much time is left before the request expires.
Results
The app updates the recipient’s DM and sends the requester a DM when the inquiry reaches a final status. If the status changes later, for example after a manual review, the app updates the same messages.
| Status (recipient DM) | Requester DM | What it means |
|---|---|---|
| ✅ Completed | @recipient has successfully verified their identity with Persona, the reason, and the verified name | The recipient completed the inquiry. This is the only status that the app calls verified. |
| ❌ Failed | @recipient has failed to verify their identity with Persona, and a link to the inquiry | The recipient did not pass the verification. |
| ⌛ Expired | Your request for @recipient to verify their identity with Persona has expired, and a link | The recipient did not complete the inquiry in time. This is not identity evidence. Do not do the requested action. |
| ✅ Approved | Persona inquiry approved, and a link to the inquiry | A reviewer or a Workflow in your organization approved the inquiry. |
| ❌ Declined | Persona inquiry declined, and a link to the inquiry | A reviewer or a Workflow in your organization declined the inquiry. |
| 🔍 Needs review | Persona inquiry needs review, and a link to the inquiry | The inquiry waits for a manual review in the Persona Dashboard. |
When the recipient reports a request, the requester gets a DM: @recipient reported on <date> that they did not make this request. If the inquiry still reaches a final status, the result DM starts with a warning that the recipient reported the request. If a reported request expires, the requester gets no second DM.
The links in the result DMs open the inquiry in the Persona Dashboard. Only people who can see that inquiry in the Dashboard can open them.
View requests in the Persona Dashboard
Each request creates an inquiry in the Persona environment that you connected, with the inquiry template that you selected. You can find these inquiries in the Persona Dashboard like other inquiries.
- The inquiry is linked to an Account with the reference ID
slack:<workspace ID>:<member ID>, where the IDs are the Slack IDs of the workspace and the recipient. All requests to the same recipient in the same workspace use the same Account. - If your template has the
requester_namefield, it shows the Slack name of the requester.
How authentication and authorization work
Persona Verify for Slack uses separate authorizations. Each one gives the app only the access that it needs.
Authorizations at installation
When an admin clicks Install Persona Verify, the Persona Dashboard gets the organization, the environment, and the user from the admin’s signed-in session. Then the admin gives three authorizations, one after the other:
Persona Dashboard ──> Persona authorization 1 (inquiries)
──> Persona authorization 2 (result notifications)
──> Slack authorization (install the bot in the workspace)
──> back to the Persona Dashboard: Connected
| Authorization | What the app can do with it |
|---|---|
| Persona authorization 1: inquiries | Read inquiry templates, create inquiries with one-time links, and read those inquiries. Scopes: inquiry_template:read, inquiry:read, and inquiry.create:write. |
| Persona authorization 2: result notifications | Create and update one webhook in your Persona environment, so that results go back to Slack. Scopes: webhook:read and webhook:write. The app never uses this authorization to create inquiries. |
| Slack authorization | Post and update its own messages, open DMs, run its slash commands, and read the names of workspace members. Required bot scopes: chat:write, commands, im:write, and users:read. The mpim:write scope, for group DMs, is optional. |
- Both Persona authorizations use the OAuth authorization code flow with PKCE. Each one must be for the same Persona organization that started the installation.
- The app saves the installation only after all three authorizations succeed. If one fails or you cancel it, no installation is created.
Authorization the first time a requester uses the command
The app never uses the installer’s Persona access to create inquiries. The first time that a requester sends a request, Slack shows a Connect your Persona account button. The requester signs in to Persona and gives the same authorization as Persona authorization 1, with the same scopes. The connection must be for the Persona organization that the workspace is connected to.
After that, the app creates each inquiry with the requester’s own Persona account, so Persona applies the requester’s own permissions. A requester can remove the connection with /persona disconnect or in Home > Settings.
A requester’s connection to Persona does not last indefinitely. It expires 30 days after the requester connects, or sooner if they do not run a command for 7 days. After it expires, the next time that they run the command, Slack shows Connect your Persona account again. The requester must connect again before they can send a request.
Data and privacy
- What stays in Persona: documents, selfies, verification results, and failure reasons. The app never posts these in Slack.
- What Slack shows: the names of the requester and recipient, the reason that the requester typed, the date, the status, and a link to the inquiry in the Persona Dashboard. When the status is Completed, the requester’s DM also shows the verified name from the recipient’s government ID.
- What Persona gets from Slack: the Slack name of the requester, in the
requester_namefield if your template has it, and the Slack workspace and member IDs of the recipient, in the Account reference ID. - What the app stores: the Slack workspace ID and name, the IDs of the Slack bot and app, the connected Persona organization, environment, and inquiry template, and the access tokens for Slack and Persona. Tokens are encrypted. For each request, the app stores the inquiry ID, the Slack IDs of the requester and recipient, the reason, the times, and the status. It does not store the verification link.
- Logs: the app does not write tokens, verification links, or signing secrets to its logs.
Troubleshooting
| Message in Slack | What to do |
|---|---|
Persona verification isn't connected to this Slack workspace, or needs to be reconnected. | A Persona admin must install or reconnect the app from the Persona Dashboard. |
Connect your Persona account to create verification links. | Click Connect your Persona account and authorize the app. Your request continues automatically. |
Your Persona connection is no longer valid. | Connect your Persona account again. |
Persona could not create a verification link: your Persona account isn't allowed to create inquiries ... | Ask a Persona admin to give you the Inquiry create and resume permissions for the selected inquiry template. |
Persona could not create a verification link: the Persona environment this workspace is connected to isn't active. | Ask a Persona admin to activate the environment. |
Persona could not create a verification link: <recipient>'s Persona account is archived. | Ask a Persona admin to restore the recipient’s Account in the Persona Dashboard. |
Persona created the verification request but could not message the recipient. | Try again. Make sure that the recipient is an active member of the workspace and not a bot. |
Mention another Slack user followed by optional context | Type the command again with an @ mention of another member. You cannot send a request to yourself. |
FAQ
Does a completed verification approve the request?
No. A completed verification tells you that the recipient passed your Persona verification. Use your usual process to decide whether to do the action.
Does the recipient need a Persona account?
No. The recipient needs only a Slack account in the same workspace. The requester needs a Persona Dashboard user.
Can I connect more than one Slack workspace?
You can connect one Slack workspace to each Persona environment.
Can I change the inquiry template?
Yes. Select a different template and click Reconnect Persona Verify.
Plans Explained
Persona Verify for Slack by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Persona Verify for Slack | Not Available | Not Available | Limited | Available |