How are Customer Seats tracked and what are the best practices for setting them up?

This article is for Flatfile's Portal 2.0, Portal 3.0, and Workspaces. If you'd like to check out the latest version of the Flatfile Data Exchange Platform, click here!

Properly setting up your user info is vital to ensuring proper billing and tracking of customer seats in Flatfile Portal 3.0. Even in a test environment, your Portals should contain proper identifying information. Do not, for example, use a different ID for each test upload, or billing errors may occur.

In your Portal, you should define the following keys:

const token = jwt.sign(
  {
    embed: EMBED_ID_HERE,
    user: {
      id: USER_ID,
      email: USER_EMAIL,
      name: USER_NAME,
    },
    org: {
      id: COMPANY_ID,
      name: COMPANY_NAME,
    },
    env: jwt.sign(
      {
        env: {
          WHATEVER: 'VALUE'
        },
      },
      SECRET_INTERNAL_PRIVATE_KEY,
      { expiresIn: '14 days' }
    ),
  },
  PORTAL_PRIVATE_KEY_HERE
)

Flatfile uses these identifiers to track customer seats for billing purposes.