What each level gives you,
and what it does not.

Because none have been set, and a number invented to make the table look finished would be a commercial commitment we never made. DocumentSynth is not generally available yet and nothing in the product charges anybody: there is no payment path, no invoice and no subscription record. When pricing is decided it will appear here, taken from the same catalogue this page already reads its limits from.

Yes — on the Free level, which is permanent rather than a trial. It does not expire, and nothing converts it to a paid level on a date. Put real documents under control on it for as long as you want, and move up when you outgrow a limit. Its seat and storage limits are the ones on the card above, which come from the server rather than from this answer. It still goes through the same review as every other request, so it is not instant: you ask for an environment and a person approves it.

By what a person can do, not by how often they sign in. A full seat is consumed by anyone who creates or revises controlled documents — tenant administrators, document owners and contributors. A light seat is consumed by reviewers and approvers, who act on documents but do not author them. Auditors and read-only users consume no seat at all, which is deliberate: an inspector should never be a licensing decision. Someone holding several roles consumes one seat, of the highest class those roles require.

The system refuses, and says so precisely. Activating a user or changing a role that would take a seat beyond the limit is rejected with the class, the number in use and the limit, rather than silently succeeding and leaving the environment over-allocated. Seats are released by deactivating someone — which is not deletion: their audit history, signatures and training records remain, because removing them would damage the record the product exists to keep.

Nothing automatic today, and we would rather say so than imply a control that does not exist. The storage figure is recorded on the environment and reported in user administration, but no upload is currently refused because of it. Treat it as the scale the level is sized for and as the point at which we would talk to you about moving up, not as a hard stop the software enforces.

The intention is month-to-month, per organization, with no annual commitment and no minimum term — a plan is a capability level, not a contract length. That is a commercial position rather than a shipped billing system: no billing interval is configured in the product today, and where this page shows an interval it is showing what the catalogue says rather than what a system is charging.

Request an environment and tell us which level you are interested in — the level travels with the request — or write to the sales address in the footer. A request is reviewed by a person, and what an environment is actually entitled to is decided at that review, not by what was selected on this page. You will get the entitlement confirmed in writing before anything is provisioned.

Yes. An entitlement is a record on the environment rather than a property of the data in it, so changing level changes seat and storage allowances without migrating anything or creating a second environment. Documents, versions, signatures and audit history are untouched by the change.