Licensing
See exactly what your install is licensed for, how much of it your people and deputies use, and ask for more in one click. The Licensing page shows who counted as a licensed user this month, how busy your deputies were against your concurrency limit, and what your install reports to Marshal. It is on your install’s admin dashboards, so you always see the same numbers Marshal does.
What you can do with it
- Check the number you are licensed on. Open Licensing and read Licensed users for the month, then export your org’s list as a CSV for finance.
- See when deputies hit the ceiling. The chart of the last 90 days shows each day’s peak against your limit. Days when launches waited are marked, with how many waited and for how long.
- Get more room fast. On a day launches waited, use Request more capacity to tell Marshal what limit you need.
What counts as a licensed user
A licensed user is a distinct person who ran a space or started a run in a calendar month (UTC). A person counts when either of these happened that month:
- They ran a space they own.
- They started a run that is not part of a deputy.
- A deputy run was attributed to them. A run you start by hand, from an ad-hoc launch or from an agent tool counts for you. A scheduled or webhook-triggered run counts for the deputy’s owner when the owner is a person. A deputy owned by a team or the org adds no one.
Each person counts once per org and once in the install total, even when they are active in several orgs. A person who counted stays counted for that month if the space, the run or the org is deleted later.
The concurrency limit
Your license can carry an install-wide limit on how many deputy runs are in flight at once. If your license has no limit, only the per-mission limits in Deputies apply.
A deputy run is in flight while it waits to start, runs, waits for a person, or is being worked on by a person. A parked run does not count.
When your deputies reach the limit:
- New launches wait and start in order as slots free up. The run shows that it is waiting for the install concurrency limit.
- Work that has already started carries on. A run that resumes after a park or a wake is never held back.
- Per-mission limits still apply on top.
If you lower the limit below what is running, nothing is stopped. New launches wait until the count drops under the new limit.
Admins also get an alert, “Deputy launches waiting on the install concurrency limit (admins)”, while launches are waiting, with a link to the Licensing page. See Alerts.
The Licensing page
Open Dashboards in the sidebar, then Licensing. Org owners and admins see it. Other members do not.
| Section | What it shows |
|---|---|
| Licensed users, for the month | Your org’s count, and the install-wide total across every org. |
| License | The state, the plan, when it expires and the concurrency limit. |
| Concurrent deputy runs, last 90 days | One bar per day for the busiest moment, with your limit as a line. Days when launches waited are colored. |
| Days launches waited | Per day (UTC): Launches that waited, Total wait and Longest wait. |
| Request more capacity | The form described below. |
| Licensed users in your org | Names and emails of your org’s licensed users, with Export CSV. |
| Organizations on this install | Licensed users and 90-day peak concurrency for each org. |
| Upload a license | For installs that cannot reach Marshal. |
| Reported to Marshal | The exact report your install last sent. See What your install reports to Marshal. |
Who sees what
| You are | You see |
|---|---|
| An admin or owner of any org | Your own org’s licensed users by name, the install-wide licensed-user total, the install’s daily peaks and throttled days, and your org’s part of the last report. |
| The owner of the install’s first organization | All of the above, plus Organizations on this install with counts per org, the whole last report, and Upload a license. |
| A member who is not an admin | Nothing. The page is for admins. |
No admin sees the people of another org. On Marshal’s hosted service, each org sees only its own figures.
Export your licensed users
Select Export CSV to download licensed-users-YYYY-MM.csv for your org. It has three columns: name, email and user_id. The export is recorded in the audit log. The list stays on your install and is never part of what Marshal receives.
Refresh license now
Your install refreshes its license from Marshal every 24 hours, and picks up any change to your limit then. To apply a change at once, select Refresh license now. Any org admin can. Repeated clicks within a minute share one refresh. You see the result, for example “License refreshed. The install now has a limit of 10 concurrent deputy runs.”
If the refresh cannot complete, the page says why and keeps the license you have:
- Marshal could not be reached. The license in force is unchanged.
- Marshal reports this license as revoked.
- Marshal does not recognise this install. Contact Marshal.
Upload a license
An install that cannot reach Marshal runs on a signed license file. The owner of the first organization selects License file under Upload a license and picks the file downloaded from Marshal. The limit in the file applies right away.
A file is accepted when Marshal signed it, it was issued for this install, it has not expired, and it is not older than the license already in force. When a file is refused, the page says which check failed:
| Message | What to do |
|---|---|
| This file is not a valid Marshal license: its signature does not check out. | Download the license again from Marshal. |
| This license was issued for a different install. | Upload the license issued for this install. |
| This license has expired. | Download a current one from Marshal. |
| A newer license is already in force here, so this older one was not applied. | Nothing. Your install already has a newer license. |
| This is not a Marshal license file. | Pick the license file itself. |
| Only the owner of the first organization on this install can upload a license. | Ask that owner to upload it. |
Request more capacity
Select Request more capacity and fill in:
- Concurrent runs you need: a whole number from 1 to 1,000,000.
- Why: Launches are waiting on the limit, Our usage is growing or Our trial is ending.
- Message (optional): up to 500 characters. It is sent to Marshal, so keep it to what the Marshal team needs to size your plan.
Each org can send one request per day (UTC). The page confirms with “Request sent to Marshal. We will be in touch.” The form links to See plans and pricing. If Marshal cannot be reached at that moment, the request is saved and goes out with the next report from your install.
Configure it
| Setting | Default | Where | Who |
|---|---|---|---|
| Concurrency limit | Set by your license | Your license, from Marshal | Marshal |
| License refresh | Every 24 hours | Automatic, or Refresh license now | Any org admin |
| Per-mission concurrency limit | Org and deputy settings | See Deputies | Org admins |
Edge cases
- Months and days are calendar periods in UTC.
- Parked runs do not count toward the limit.
- A scheduled or triggered run of a team or org deputy adds no licensed user.
- If your install cannot refresh its license, the limit last known stays in force.
Try it
Open Dashboards, then Licensing, and select Export CSV to see the people who count this month.