Teams

An Organization is a shared Parsli account. Parsers and credits belong to the organization rather than to one person — so work does not disappear when someone leaves, and billing stays in one place.

What is shared

Parsers. Members see the organization's parsers, subject to their role. One person sets up a supplier-invoice parser and the whole finance team uses it.

Credits. One balance, one invoice. Anyone's extraction draws from the same pot. See Shared credit pool.

Documents and results. Everything extracted belongs to the organization.

Roles

Four roles, strictly hierarchical — each includes everything below it.

Member is the right default for people doing the work. Viewer suits an accountant or auditor who needs to see output without the ability to alter a field definition — a changed definition changes what future documents produce, which is not a change you want made casually.

Only an owner can transfer ownership. Do that before the current owner leaves, not after.

Adding people

Invite by email from Settings. They receive an invitation and join with the role you assigned.

For a company domain, domain-based joining lets people with matching email addresses join without an individual invitation — convenient for a team of thirty, and worth thinking about before enabling: anyone who can get an address on that domain can join.

Letting people send documents without accounts

Not everyone who has documents needs an account. Two lighter options:

• The parser's Inbound email address — anyone who can send email can send documents.
• The Inbox — a shared drop-off point with its own access rules.

Both mean colleagues, suppliers, or clients can get documents in without occupying a seat or gaining access to your results.

Watching the shared balance

A shared pool means one person's bulk import can consume the month for everyone.

• Check usage in Settings.
• Iterate on field definitions with a one-page sample, not the full batch.
• Remember that reprocessing charges again — a definition change re-run across a large archive is a real cost.

Departments, budgets, and approvals

If your account is an organization, a Budget page appears in the sidebar for admins and department heads. Each parser's Settings then has a Budget & approval section, where you nominate the field holding the document's amount, track it against a department budget, and optionally require a department head to approve before the document proceeds.

That covers attributing spend and gating documents on a person. The full process built around it — vendors, bills, routing, and the screens to run them — is a premium workspace.