Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tight.com/llms.txt

Use this file to discover all available pages before exploring further.

If your platform uses a popular identity provider, like Auth0, AWS Cognito, Okta, or Stytch, then you can authenticate your users to Tight Embedded Accounting by following the steps below (no developer required).

​
Securely sharing your JWKS path

Simply use the Configure Identity Provider API to specify your Identity Provider and Issuer URI.

​
Configure business-specific attributes

Tight will use the standard user claims (attributes) included by your identity provider, like email, name, etc. Additionally, you can set up the following optional company-specific attributes in your identity provider:
ClaimDescription
companyNameName of the user’s company
entityTypeThe type of the entity (SOLE_PROPRIETORSHIP, LLP, LLC, S_CORP, C_CORP)
companyIdId of the company in your DB
addressAddress of the company

​
Get a JWT access token

​
Ready-to-Launch

If you are using Ready-to-Launch accounting, then you simply need to route your user to the Ready-to-Launch app. The RTL app will take care of the authenication using your identity provider.

​
Embedding Tight

If you are embedding accounting into your existing UX, then you can obtain a JWT from your identity provider, and simply pass that JWT into the front-end components as the access token.