Administration – Latenode

This article describes the user authorization process for your organization and the capabilities of the administrator panel within the Latenode platform.

Requirements

To follow the steps described below, you must already have a White Label administrator account on the Latenode platform, as well as a secret key for signing JWT tokens.

Creating Custom Subscription Plans

Before you begin authorizing users from your organization within the Latenode platform, you need to create at least one subscription plan that will be automatically assigned to new users.

Initially, your organization will be provided with defined maximum and minimum values for various characteristics that can be configured for each plan. These characteristics are referred to as quotas.

List of configurable characteristics and quotas for your organization:

Execution Microcredits

1 platform credit equals 1 million microcredits. Depending on the minimum execution fee (see corresponding section), users may spend less than 1 credit per scenario execution.

Plug&Play Microtokens

1 token equals 1 million microtokens. Used for Plug&Play nodes (e.g., AI nodes without connection setup), as well as for some integrations.

Active Scenarios Limit

Parallel Executions Limit

Min Execution Charging Period (Microseconds)

1 second equals 1 million microseconds. By default, 1 credit (1 million microcredits) is charged for every 30 seconds of scenario execution. You can reduce the charging interval. For example, setting it to “3000000” will charge 0.1 credit (or 100,000 microcredits) every 3 seconds of execution.

AI Assistant Requests Limit

Connected Accounts Limit

Minimum Trigger Interval (Seconds)

Execution History Availability Period (Minutes)

In the admin dashboard, these quotas can be found in the “Plans” section:

To create a new plan, click the “Create Plan” button. A form for creating a new plan will appear:

Fill in the plan name and its characteristics, as described above, for example:

After clicking “OK”, a new entry will appear in the plans table. You will later need the ID of the created plan. You can find it in the “ID” column:

User Authorization in the Platform

We’ve prepared a sandbox repository for experimenting with user authorization. Instructions for running it can be found in the repository's README.md.

Once the sandbox is running, open the “JWT Generation” section:

This section helps you generate a JWT token for a user in your organization. With this token, you can authorize the user in the embedded mode of the Latenode platform.

To generate a JWT token, you need to:

Paste your private key into the “Private Key” input field and select the signing algorithm corresponding to your key pair.

Fill in the Tenant ID, User ID, and Plan ID fields, where:

Tenant ID – Required. Your tenant ID in the Latenode platform

User ID – Required. A unique string that clearly identifies the user in your organization

Plan ID – Optional. The ID of the subscription plan to be assigned to the user during their first login. For future logins, this field is not required. In this example, the created plan ID is “35”

The completed form may look like this:

Click the “Generate Token” button to create a new JWT token, which you can copy using the “Copy” button:

💡

Token generation is done locally without network requests. This ensures your private key is not sent to the Latenode platform or any third parties.

Once the JWT token is generated, go to the “White Label” section. Paste the copied value into the “JWT Token” field. In the “UI Config JSON” field, insert the following:

{
  "scenarios": {
    "hideEmptyScenariosGreetings": true
  },
  "main": {
    "hideSideMenu": false
  }
}

Then click the “Init” button. After that, an embedded version of the Latenode platform will appear on the right side of the screen, with the new user already authorized, in this case with ID = my_test_user_1

Acting as this user, create a scenario and run it to reduce the user’s credit balance. Since the minimum execution fee in this plan is 3 seconds, you need to run a “heavy” scenario to deduct at least 1 credit. For example, you can use a JS node with the following code:

export default async function run({execution_id, input, data, store, db}) {
	await new Promise(res => setTimeout(res, 29000));
	return {

	}
}

This code runs for 29 seconds, which corresponds to a 1-credit deduction:

Subscription Management and Resource Usage Monitoring

To view the list of existing subscriptions, go to the “Subscriptions” section:

Here, you can see total credit and plug&play token usage for the current billing period:

You’ll also see a table of usage per subscription for each user, with an option to cancel subscriptions:

To add a subscription for a user, click the “Add Subscription” button:

In the modal window, select the user and the subscription plan to assign:

Managing the User List

To view the user list, go to the “Users” section. On this page, you can see the list of users along with their assigned subscriptions. The subscription assignment functionality is also available here: