Docs

    Manage your organisation

    Team and Company subscriptions are organisations with seats. Org admins manage everything from the account page at app.ansvar.eu/account, with no support ticket needed for the day-to-day.

    Seats and roles

    The Organization section lists members and pending invites, above a seat line that counts the seats your subscription pays for: people, plus service credentials past the five that Team and Company include without a seat (on Premium every credential takes a seat). Admins can:

    • Invite a member by email. They get a seat and an activation email. Someone who already has an Ansvar account in your organisation gets the seat at once, with no email; adding a current member changes nothing. If every seat is in use, the invite is refused with seat limit exceeded: raise the seat count under Manage subscription first.
    • Change roles: member or admin. A member must have accepted their invite before their role can change.
    • Revoke a seat: removing a member frees the seat immediately. You can't revoke your own seat; another admin has to.

    Every seat inherits the organisation's tier. There is no per-seat tier mixing. Team and Company search quotas are pooled across the organisation, not per seat.

    Standard seats

    Licensed ISO standards are sold as seats. Your organisation buys a number of seats of a standard, and an admin assigns each one, under Standards & documents, to a person or to a service credential. A credential holding a standard seat is an agent that can cite that standard.

    • One seat, one holder. There is no organisation-wide conferral: a standard reaches exactly the people and credentials you assign it to.
    • A standard seat is not an organisation seat. The two are counted and bought separately, and a standard seat does not consume one of your member seats.
    • Release returns the seat to the pool to assign again. Revoking a credential releases any standard seat it held, so a paid seat is never stranded on a dead identity.
    • If your seat count drops below what is assigned (you reduced the subscription, say), the excess seats are suspended rather than deleted. They are shown as suspended and are not served; release one to bring the rest back into use.

    Seats of a standard are the same price whoever holds them. Volume discounts are available on request: talk to us if you need seats in bulk.

    Subscription and billing

    The Plan & billing section shows the plan, billing cycle, renewal date, and invoices. The subscription rows are read live from Stripe. Seat-count and plan changes go through Manage subscription. EU VAT IDs are validated on entry and reverse-charge is applied where it applies. Company details (legal name, billing country, VAT ID) sit at the bottom of the same section.

    Account security

    The Account & security section covers profile details, password reset, two-factor authentication, email verification, active sessions, and connected agents. Sign-in supports username + password, Microsoft Entra ID, and Google. Sessions and OAuth clients authenticate against auth.ansvar.eu.

    Audit exports and the audit ledger

    The audit ledger (Company tier) is the tamper-evident record of gateway usage: every query generates a cryptographic receipt of what was asked, what was returned, and when. There are two ways to it, and neither is a browsable log: the account area exports bundles, it does not display a feed:

    • From the account area. The Audit exports section (Company tier) downloads a bundle for a date range. An org admin gets the signed, tamper-evident organisation-wide bundle, the one an auditor checks offline; a member of that organisation gets their own receipts, for their records. That file holds part of the receipt chain, and the offline verifier rejects gaps in the chain and missing receipts on signed days. Team and lower have no audit section. The entry is padlocked and names Company as the plan that opens it.
    • From your agent. get_receipt / list_receipts / verify_receipt read the ledger, and export_audit_package produces the same offline-verifiable bundle. Receipts are encrypted; they decrypt client-side with your tenant's key (decrypt_receipt), so Ansvar can't read them for you.