Trying to understand how licensing is working now

It used to be that you had a per seat licensing setup, this was great for shift work when it came to development. Currently from what I’m seeing it’s a per user licensing setup and the only way to shift licenses is to manually go into Orchestrator and delicense a user in my licensing group.

Is there currently a way to release a user license when they sign out or disconnect, or are we stuck with having to manually go in and do it?

Only through Orchestrator UI:

Approach #1 (for Cloud Orchestrator when you have the User License Management enabled with an Admin User)

Admin → Organization name → License

Approach #2 (As a user that has the privileges to View/Edit users and robots)

Orchestrator → Tenant → Manage Access → find the Attended user in the list → in the Personal Automations setup → disable the Enable user to run automations → Update

Note: you can do it programmatically with RestAPI calls. For this, use the browser’s Inspect tool while you are performing the above steps. Take a note for the Rest API calls which are made and do the same in your third party scripts or programs.

1 Like

I saw those, will they work with the current documented api calls for authentication?

You will need to use the access_token in your future calls

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.