Tally

Probo reads your Tally organization’s users and pending invitations through the Tally API so you can review who has access.

Caution

Use a Tally API key (tly-…) created under Settings > API keys. Tally ties each key to the user who created it, so the key inherits that user’s permissions and stops working once that user leaves the organization. Create it from an account that can read the organization’s members and that will stay in the organization.

Prerequisites

• Probo organization administrator access
• A Tally account in the organization you want to review, preferably the organization owner. A key has no scopes of its own: it inherits the permissions of the user who created it, so calls made with the key can do no more than that user can

Probo resolves the organization from the key, so the Connect dialog asks only for the key.

Collected Fields

Probo field	Tally field	Notes
Name	fullName	A pending invitation carries no name
Email	email	A record with no email address is skipped
Role	invites	Tally exposes no role on an organization user, so members have none. A pending invitation is listed with the role Invited
Admin	Not supported
Status	isDeleted	A user flagged isDeleted is listed as inactive and every other user as active. Pending invitations are listed as inactive
MFA	hasTwoFactorEnabled	Enabled when the flag is true, disabled when it is false. A pending invitation carries no flag, so its MFA state is left unknown
Last login	Not supported
External ID	id	Stable identifier used to track the account across reviews. A pending invitation is keyed by its invite id
Created at	createdAt	The timestamp Tally returns on the user record. Probo does not record one for a pending invitation

People who have been invited but have not yet accepted appear alongside the organization’s users, marked inactive.

Step 1: Create an API Key

1. In Tally, signed in as the account the key should belong to, go to Settings > API keys.
2. Click Create API key, name it (e.g. Probo Access Review), and click Create. Tally keys have no scopes, so there is nothing to set on the key.
3. Copy the key (tly-…) and store it securely. Tally shows it only once.

Step 2: Connect in Probo

1. In Probo, go to Access Review > Connections.
2. Find Tally, click API Key, paste the key, and click Connect.

Probo checks the key against the Tally API before it creates the connection, so a rejected key fails at the Connect step and never becomes a broken source. Probo resolves the organization the key belongs to and names the source after the organization owner, because the Tally API exposes no organization name.

Troubleshooting

• Tally rejected the API key. The Connect dialog shows this error when the key fails the check against the Tally API. Confirm the value is an active Tally API key (tly-…) copied from Settings > API keys. A key also stops working once its user is removed from the organization or leaves it, so create a replacement from an account that is still a member.
• The source connects but fails to sync. The Connect check only proves Tally accepts the key. The sync then reads the organization’s users and invites with that key, and it can do no more than the key’s user can, so an under-permissioned key passes Connect and fails later. Create the key from the organization owner’s account instead.
• Few or no members appear. A Tally account belongs to a single organization, and inviting team members is a Tally Pro feature, so a Free account’s organization typically has only that one member.