Connections
Connections determine what Alma can see and where it can act. Every workflow you build depends on the connections you set up here.
Organization and personal connections
Organization connections are connected once, by one person, on behalf of the whole company — a shared Slack workspace, the company GitHub org, your Linear workspace.
Personal connections are an individual’s own account — their Gmail, their calendar. Only they can connect it. You can require it, and Alma will ask them, but you can’t connect it on their behalf.
Some tools appear in both lists because they’re genuinely two different connections with separate permissions — the company’s shared Slack account and a member’s own Slack account, for instance. The same applies to Zoom, GitHub, and Microsoft 365 (SharePoint for the org, OneDrive for the person). Each entry cross-links to its twin.
The lists show requirements, not a catalog
The two lists on this page show what your org has chosen to require — not everything Alma supports.
An entry appears under Organization because someone required it for the company. An entry appears under Personal because someone — a person, a group, or everyone — is required to connect it.
To add something, use Require a connection. The picker shows the full catalog.
The catalog is managed by Alma, not by your workspace. You choose what to require and connect from it, but you can’t add a new integration to it yourself. If something’s missing, email help@alma.team.
Coverage and reminders
The coverage card tracks personal-connection rollout: how many required people have connected, a progress bar, and who’s outstanding. It appears only while gaps exist.
Remind and Remind all send real reminder emails. Alma re-checks each person’s connection status before sending, so someone who just connected isn’t nagged. Anyone reminded in the last 7 days is marked as recently reminded.
Use the coverage card on this page to send reminders. The per-person Remind button on a connection’s People tab looks identical, but doesn’t send an email. See Requiring connections.
Delegation
If the person setting up Alma doesn’t own an account, delegate it to the teammate who does. They get an email, connect it from their own settings, and their row shows Pending until they finish, then Connected.
Delegations can be revoked at any time.
Connection tabs
| Tab | Org | Personal | Purpose |
|---|---|---|---|
| Overview | ✓ | ✓ | Who connected it, delegation, coverage |
| People | ✓ | Who’s required individually | |
| Groups | ✓ | Which groups require it | |
| Tools | ✓ | ✓ | What Alma can do with it, and who’s allowed |
| Access | ✓ | ✓ | The rules that decide that |
| Log | ✓ | ✓ | Every call Alma has made through it |
People and Groups exist only for personal connections, since an org connection has a single account.
Tools, Access, and Log are a scoped view of one workspace-wide ruleset, not per-connection config. A rule written on the Slack connection’s Access tab is the same rule shown under MCP → Permissions, and it applies everywhere Alma runs, not just to Slack or over MCP. See Tools & access.
Disconnecting
Disconnect stops Alma reading through that account immediately. You can reconnect any time.
Remove from required clears every requirement aimed at that connection — org, group, and individual — and removes it from the list.