Skip to content

Enrollment

Enrollment is the process of connecting a new Comers Core instance to the selected Organization in Comers Start.

It is used only for the first connection of the instance.

It is not part of day-to-day sign-in to Comers.

Enrollment creates a link between:

  • the Organization in Comers Start,
  • the Core instance,
  • the Core Organization used inside that instance,
  • the subscription and permissions needed for Core to operate.

This lets Comers know which customer the instance belongs to and which services and features it can use.

flowchart TD
    O[Platform Organization] --> T[Enrollment token]
    T --> E[Core enrollment]
    E --> I[Core instance]
    I --> C[Core Organization]
    C --> R[Ready for launch]

To connect a new Core instance:

  1. select the Organization you want to link it to,
  2. open Instances or start adding a new instance,
  3. generate an enrollment token,
  4. open the configuration link you receive,
  5. finish connecting the instance in the Core panel.

The token is created for the selected Organization, so before generating it make sure you are working in the correct context.

An enrollment token is a one-time code used to securely connect one Core instance to the selected Organization.

The token is valid only for a limited time and should be treated as confidential.

It is not used for:

  • user sign-in,
  • day-to-day API use,
  • launching an already connected Core instance.

After the instance has been connected, the token is no longer needed for normal work with Comers.

After you generate the token, Comers guides you through configuring the new Core instance.

In simple terms, the process is:

  1. generate the token in Comers Start,
  2. open the Core configuration link,
  3. Core uses the token to confirm the link to the selected Organization,
  4. finish configuring the instance,
  5. once completed successfully, Core is ready to use.

The token is needed only during this process.

After configuration is complete, you use the normal Comers sign-in for day-to-day work.

During the first Core setup, you can select an existing Core Organization or create a new one.

It is then linked to the Organization you selected earlier in Comers Start.

In a typical setup, both Organizations represent the same company and can have the same name.

They are stored separately because Comers Start and Core are responsible for different areas of the system.

To better understand the difference between an Organization in Start and an Organization in Core, see the typical and advanced setup section on the Comers Platform page.

With the self-hosted version, the user participates directly in connecting the instance to Comers Start.

In practice:

  1. generate an enrollment token in Comers Start,
  2. use it while configuring your Core installation,
  3. once connected correctly, the instance appears in Start and can be launched by authorized users.

Detailed documentation for installing and maintaining the self-hosted version will be available separately.

For Core maintained by Comers, most of the instance connection process can be completed automatically.

This means the user usually does not need to manually generate or copy a token unless a particular setup process requires it.

Whether you use self-hosted Core or Core maintained by Comers, the result is the same: the instance is linked to the correct Organization and can be launched from Comers Start.

Enrollment and launching Core are two different stages.

Enrollment is used to connect a Core instance to an Organization for the first time.

You do this while configuring a new instance.

Launching Core is used for the user’s day-to-day entry into an already configured instance.

In the simplest terms:

Enrollment = you connect Core

Launch = you enter Core

The enrollment token is used only to connect the instance and is not used for opening Core day to day.

After the instance is connected successfully, it appears in Comers Start under the correct Organization.

When the instance is active and you have the appropriate permissions, you can launch it directly from Start and begin working in Core.

From that point on, enrollment is no longer part of day-to-day work.

Continue with Core instances and then Business structure.