Quick Answer
Create a scoped token for each third-party connection
Open Settings → Other Settings → Private Integrations, create a named integration, grant only the necessary permissions, generate and securely store its token, and use that token when authenticating API requests.
Connecting Tools Without Giving Away Full Access
You may need to connect BizStackPro to another application, but broad API access can create unnecessary security risks.
Private Integrations allow you to control what each connection can access by assigning specific scopes and permissions.
Without appropriate controls, an integration may have access to more information or actions than it needs, making that connection harder to manage securely.
Private Integrations provide fixed OAuth2-style access tokens with scoped permissions, offering more control than broad, all-or-nothing API keys.
Simplicity
Generate and manage integration tokens directly from the account settings.
Security
Restrict each connection to the permissions it requires by applying the principle of least privilege.
Modern API Access
Use newer API versions and webhook-based automation with controlled access.
At a Glance
Primary purpose
Secure third-party application access
Access control
Scoped permissions
Default creators
Account administrators
Recommended rotation
Every 90 days
Before You Begin
Define the purpose and required access before generating a token.
- Identify the third-party application that will use the token.
- Determine which BizStackPro information and actions the application actually needs.
- Select only the scopes required for that purpose.
- Prepare a secure password manager or secrets vault for storing the token.
- Confirm who will maintain the integration and rotate its token.
- Review Roles & Permissions if integration creation should be limited to specific administrators.
Where to Find Private Integrations
In BizStackPro, go to Settings → Other Settings → Private Integrations .
If Private Integrations does not appear, check Labs and enable the corresponding feature toggle.
Administrator access: By default, all account administrators can create Private Integrations. You can limit this ability under Roles & Permissions.
Create a Private Integration
Create a separate, clearly identified integration for the application you want to connect.
1. Open Private Integrations
Go to Settings → Other Settings → Private Integrations .
2. Create a new integration
Select Create New Integration.
3. Name and describe the connection
Enter a clear name and description identifying the application, purpose, or person responsible for it.
4. Select the scopes
Grant only the permissions required for the integration to work. Avoid adding unrelated access.
5. Generate and copy the token
Select Generate Token and copy the token immediately. You will not be able to view it again.
Protect the token: Store it in a password manager or secrets vault. Never place tokens in chat messages, screenshots, or unprotected plain-text documents.
Use the Token in API Calls
When a third-party application calls a BizStackPro API, send the
Private Integration token in the
Authorization header as an access token.
Permission changes: You can change an integration’s scopes without automatically generating a new token. The existing token remains valid, but its permitted actions change with the assigned scopes.
Manage, Edit, or Delete Integrations
Edit the details
Update an integration’s name or description when its purpose, owner, or connected application changes.
Adjust the scopes
Add or remove permissions as necessary while continuing to follow the principle of least privilege.
Delete unused integrations
Open an integration and select Delete when the connection is no longer needed.
Important: Editing an integration’s name, description, or scopes does not automatically generate a new token.
Security and Token Rotation
Treat every Private Integration token as a credential that can access your BizStackPro account according to its assigned scopes.
Rotate tokens every 90 days
Routine rotation reduces the length of time an old or unknowingly exposed credential can remain useful.
Expire old tokens
After the replacement token is active in the connected application, expire the old token.
Respond to access changes
Rotate tokens immediately after staff or vendor turnover or whenever exposure is suspected.
If a token is compromised: Rotate it immediately in the BizStackPro settings and update the token in every connected application or service.
Frequently Asked Questions
What is a Private Integration?
It is a secure way to connect BizStackPro to third-party applications using scoped access and support for newer API features.
How are Private Integrations different from API keys?
They provide finer-grained access controls and support newer API versions and webhooks.
Who can create Private Integrations?
All account administrators can create them by default. This can be limited under Roles & Permissions.
Where can I find Private Integrations?
Find them under Settings → Other Settings → Private Integrations . Enable the feature through Labs if it is not visible.
How do I create one?
Create a new integration, enter its name and description, select the necessary scopes, and then generate and copy the token.
How do I keep tokens secure?
Store tokens securely, rotate them at least every 90 days, and expire old tokens after the replacements are active.
What if a token is compromised?
Rotate the token immediately in the settings and update the credential in every connected application.
Can I edit permissions without changing the token?
Yes. You can update the name, description, or scopes while the existing token remains valid.
How do I delete a Private Integration?
Open the integration in the settings and select Delete.
How often should I rotate tokens?
Rotating tokens every 90 days is recommended to maintain security.
