Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
AI connections and developer tools

Understand a private app’s beta company invitation

The invitation makes authorization possible; the customer still must approve access.

Updated 2026-11-11

Invite a beta company allows a specific Institution company to authorize your private developer app during the invitation period. Enter the customer’s exact Institution company ID.

The invitation itself grants no data access. The customer still completes your normal OAuth flow, signs in, selects the eligible company, and approves the displayed permissions.

Check the invitation’s expiry in Developer apps and ask the customer to authorize within that window. If the company ID is wrong, correct the invitation rather than sending a different customer through a link that will not make their company eligible.

Use Revoke beta access when the company should no longer participate. A beta invitation is also separate from directory approval: it supports a private test audience, not automatic publication to all customers. Keep the app’s requested scopes limited to the intended test and confirm the environment before submitting live source data through the authorized connection.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.