> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/administrator-guide/licensing/managing-a-license.md).

# Managing a License

When you do not have a license, you can still run the Flopsar environment with some limitations. Collecting data from agents requires a valid license uploaded on the License page in the Workstation.

Paste the license content into the update form. The license sets the maximum number of agents that can collect data, and an expiry date unless it is permanent. When the license expires, licenses are revoked from connected agents until a single agent remains, and collection almost stops.

## License Allocation for Agents

### Automatic assignment

If the number of connected agents is at or below the licensed maximum, every agent receives a license automatically.

### License limit exceeded

If more agents connect than the license allows, only a subset is licensed. The server chooses which agents receive a license using internal criteria.

### Manual assignment

To control which agents are licensed, assign licenses to specific instances. This overrides automatic allocation and is the way to keep critical agents licensed when you are over the limit.

{% hint style="warning" %}
You need the **Edit license mapping** permission to change license mapping.
{% endhint %}

## Best Practices

* Prioritize agents that matter to production when assigning licenses manually.
* Review license use against the number of connected agents.
* Plan capacity before you add instances, rather than relying on manual mapping as the steady state.