Frequently asked questions
This page is for people who use or administer Actagate and want to go from a symptom to its cause and fix. Each question lists the symptom, the cause, the fix and related pages. Pick the symptom that matches yours from the contents below.
Cannot sign in
I cannot sign in to the Web app
Symptom: Sign in with Slack ends with not_registered, and the page says "This Slack user is not registered in the user ledger."
Cause: Sign in with Slack works only for Slack accounts already registered in Actagate. You are not registered yet, or you were invited by email.
Fix: Run /actagate or use a stamp in Slack once to register, then try signing in again. If you were invited by email, use the email sign-in on /login instead.
Related: I did not receive the email, SSO troubleshooting
I cannot sign in with SSO
Symptom: After you sign in with an SSO button, you land back on the login page with a message. Or you can no longer sign in with an email link or Slack.
Cause: The value of error= in your browser's URL is the reason code. For example, error=invalid_connection means that login connection cannot be used. The login page body does not display the code itself. The common codes are:
| Reason code | Login page message | Meaning |
|---|---|---|
test_required |
The SSO settings changed. Start sign-in again. | The connection settings changed during sign-in, or the connection went back to draft |
invalid_callback |
The login response could not be verified. Please try again. | More than 10 minutes passed since sign-in started, or you returned in a different browser |
sso_required |
Sign in with SSO for this organization. | The organization requires SSO. Nobody can sign in with Slack, and only owners can use an email link |
invalid_connection |
This login connection is unavailable. | The connection is disabled or cannot be found |
Fix:
- For
test_requiredandinvalid_callback, start sign-in again from the beginning in the same browser. Iftest_requiredkeeps appearing, an administrator tests and activates the connection - For
sso_required, use the SSO button on the login page - For
invalid_connection, an administrator checks the state of the connection - For any other code, look it up in SSO troubleshooting. If the problem continues, send the code to your administrator. Administrators can also check the reason code in the
auth.failedaudit event
Related: SSO troubleshooting, Verify domains and require SSO
Cannot submit a request
I am asked to set my manager
Symptom: When you submit a request, you see "Set your manager with /actagate setup".
Cause: The approval route includes your manager, but you have no manager set, or your manager's account is disabled.
Fix: Run /actagate setup @your-manager once in Slack. An administrator can also set it in Members.
Related: Slack commands, Invite members, set managers and roles
I submitted a request by mistake
Symptom: You submitted a request you did not mean to send.
Cause: A request enters its approval route as soon as you submit it.
Fix: While the request is still pending, withdraw it yourself with "Withdraw" on the request details or in the Slack confirmation DM. A withdrawn request stays under "Needs attention" in "My requests" and ends there unless you resubmit it. An emergency post-approval cannot be withdrawn. For an approved or executed request, an Owner or Admin uses "Revoke" in the ledger to invalidate the issued item while retaining the record.
Related: Guide for requesters
Cannot approve
It says I am not the approver
Symptom: When you press a button on an approval card, Slack displays "You are not the approver for this step."
Cause: Only the following people can act on a step. Anyone else gets this message.
- On an individual step, the assigned approver
- On an individual step, a delegate of that approver, while the delegation period is running and the delegation has not been revoked. Delegates cannot act on approval group steps
- On an approval group step, anyone who is a member of the group at the moment they act
If you are the requester, you cannot act even when one of these applies. The same is true when your account is disabled. On an individual step, nobody can act (delegates included) when the assigned approver's account is disabled.
Fix:
- If it is your own request, leave it to another approver (see the next question)
- To approve on someone's behalf, ask the approver, or someone who can manage members (Owner, Admin or Member admin), to name you as the delegate under "Approval delegation" in Settings (
/ws/settings). An expired delegation no longer works - For an approval group step, ask an administrator to add you to the group
Related: Guide for approvers, Approval groups
I cannot approve my own request
Symptom: You cannot approve, reject or return a request you submitted. Slack displays "You are not the approver for this step."
Cause: Requesters cannot act on approval steps for their own requests. This applies to approval, rejection, and returns on the Web, in Slack, through approval groups, and as a delegate.
Fix: To test by yourself, use two accounts, one for requesting and one for approving. Alternatively, ask an administrator to change the manager or catalog approver to another person, then submit a new request. Configuration changes do not alter an existing request's approval route.
Related: Approval groups, Guide for approvers
Slack
A stamp is not recorded
Symptom: You add a stamp, but "Recorded" does not appear.
Cause: The Bot has not been invited to that channel.
Fix: Run /invite @Actagate, then remove the reaction and add it again.
Related: Guide for requesters, Connect Slack
The slash command does not respond
Symptom: /actagate says "app did not respond".
Cause: Slack shows this when a slash command does not answer within 3 seconds. Either the Bot is down or its Socket Mode connection has dropped.
Fix: Wait a minute, run /actagate again, and contact an administrator if it still fails. Administrators check the state with docker compose ps bot and read docker compose logs --tail=100 bot. The health check is http://127.0.0.1:3001/healthz, and docker compose restart bot brings it back.
Related: Slack commands, Connect Slack
The Slack card after approving on the Web
Symptom: You approved on the Web and are not sure what happens to the Slack approval card.
Cause: The Web and the Slack approval card point to the same approval step.
Fix: You do not need to do anything. When you approve, reject, or return on the Web, the corresponding Slack approval card is updated to the same result; acting in Slack likewise updates the Web. A request is never processed twice, and regardless of where you act the audit record and plan-hash verification are identical.
Related: Guide for approvers
I did not receive the email
Symptom: A sign-in link or an invitation does not arrive.
Cause: The message went to spam, the address differs, the link expired, you hit the rate limit, or sending is not configured.
Fix: Check the following in order.
- Look in your spam folder. The sender is the
MAIL_FROMaddress configured by your administrator - Make sure the address you entered is the one your administrator invited (case does not matter). The screen responds the same way whether or not the address is registered, so ask an administrator for an invitation if you are not registered yet
- Links expire after 15 minutes and can be used only once. If yours expired, request a new one from
/login - Requesting too many links in a short time is rate-limited (five per hour for the same address). Wait a while before trying again
- If it still does not arrive, contact an administrator. Administrators check the following. With
MAIL_TRANSPORTleft atlog, nothing is actually sent and the message only appears in the server log. ChecksmtpwithSMTP_URL/MAIL_FROM, and the SPF / DKIM records of the sending domain
Related: Environment variables, Notifications
The invitation email does not arrive
Symptom: You were invited, but no email lets you sign in. The link in the invitation only opens the login page.
Cause: When the organization requires SSO, Actagate sends no sign-in emails to anyone except owners. Entering your address on /login shows the usual response, but no email arrives. The invitation email is still sent, but its link only opens the login page. Owners keep receiving sign-in emails while SSO is required.
Fix: Sign in with the SSO button on the login page. If SSO is not required and the invitation itself does not arrive, go through I did not receive the email.
Related: Verify domains and require SSO, Invite members, set managers and roles
Settings and permissions
I cannot see the workspace
Symptom: Opening the workspace at /ws/* sends you back to Home (/home?message=workspace_unavailable).
Cause: Only people who approve, administer or audit can enter the workspace. You can enter if any of the following is true: (1) your role is Owner, Admin, Catalog admin, Member admin or Auditor, (2) you are someone's manager, (3) you are a member of an approval group, or (4) you are assigned as the approver on an approval step, or have acted on one.
Fix: If none of these applies, use Home. When you only need to approve, you can also act from the Slack card.
Related: Roles and permissions, Guide for approvers
Some workspace menu items are missing
Symptom: You can enter the workspace, but Catalog, Members, Observability, Reports or Settings is missing from the menu.
Cause: The menu shows each item only to roles that hold the matching permission.
| Menu item | Roles that see it |
|---|---|
| Catalog | Owner, Admin, Catalog admin |
| Members | Owner, Admin, Member admin |
| Observability, Reports | Owner, Admin, Auditor |
| Settings | Owner, Admin |
Approvals, Requests, Cloud operations and Ledger appear for everyone who can enter the workspace. Stamps appears only while the organization is connected to Slack.
Fix: Ask an Owner or Admin to give you the role you need. If Settings is not in your menu, you can still open /ws/settings directly to change the display language, approval delegation and login methods.
Related: Roles and permissions, Invite members, set managers and roles
I ended up with two accounts
Symptom: The same person has two rows in Members. Depending on how you sign in, you land in a different row.
Cause: A row imported from Slack and a row invited by email have different email addresses, so they became separate rows. Or first-login provisioning (JIT) for SSO created a row with a different email address from the existing one.
Fix:
- Before merging, check that no approval is pending between the two rows. If a merge makes the requester and the approver the same row, that person cannot approve the step afterward
- An Owner, Admin or Member admin opens Members (
/ws/members), chooses "Source account" and "Keep account" under "Merge accounts", and presses "Merge". A merge cannot be undone - After the merge, every session and sign-in link of both rows expires. The person signs in again
Related: Manage login methods and merge duplicate accounts
An SSO setting shows a reason code
Symptom: Under Settings, Security (/ws/settings/security), verifying a domain or disabling a connection fails with a reason code.
Cause: The common codes are:
| Reason code | Message | Meaning |
|---|---|---|
domain_taken |
Another organization has verified this domain. | Only one organization can verify a given domain |
enforcement_active |
Turn off SSO enforcement before disabling the last active connection. | While SSO is required, you cannot disable the last active connection. Changing authentication settings in a way that sends the last active connection back to draft is refused the same way |
Fix:
- For
domain_taken, confirm which organization should verify the domain - For
enforcement_active, turn off "Require SSO" first, then disable the connection. If another connection is active, you can disable one of them without turning off the requirement - Look up any other code in SSO troubleshooting
Related: SSO troubleshooting, Verify domains and require SSO
I want to change the language
Symptom: You want the Web app or Slack in another language.
Cause: The display language is a single setting used by both the Web app and Slack notifications.
Fix: Use 🌐 in the upper-right corner of the Web app, or "Display language" in "Settings"; the selection is saved and Slack notifications use the same language. If your account is linked to Slack, the setting is overwritten with your Slack language whenever you use a command or stamp in Slack or sign in with Slack. To keep one language, set the same language in Slack.
Related: Guide for requesters
I want to know where data is stored
Symptom: You want to know where requests and chat content are stored.
Cause: Actagate is self-hosted.
Fix: Data is stored in your organization's self-hosted PostgreSQL database. Chat content is stored only as an excerpt from a message to which a stamp was added.
Related: Security and data handling