Skip to main content
PlanRelevé Wiki

Organization administration

Organization administration centralizes member access, security, storage, tax, AI, MCP, audit and branding controls. These settings affect everyone in the organization, so review them with the person responsible for bids, privacy and identity management.

PlanRelevé Organization administration dashboard showing active users, pending invitations, projects, storage usage, AI controls, security, MCP status, tax groups, audit and branding for a fictitious organization.
PlanRelevé Organization administration dashboard showing active users, pending invitations, projects, storage usage, AI controls, security, MCP status, tax groups, audit and branding for a fictitious organization.

Access and role limits

UI path: account menu (your initial, top right) → Administration. The page is titled Organization administration.

Only an organization Owner or Admin can open these pages and their Users, Invitations, Security, Storage, Tax groups, MCP server, Audit & data and Branding controls. Project managers, Editors and Viewers are refused (403) if they try to use them. A role granted on a project does not give access to organization administration.

The dashboard summarizes active and total accounts, pending invitations, active and archived projects, used and included storage, the current AI tier and the MCP Enabled or Disabled status.

Owner and Admin have almost the same controls. One important limit remains: only an owner can make or invite an owner, or demote, deactivate or delete an owner. The organization always keeps at least one active owner; transfer ownership first.

Manage users and invitations

  1. Open Users to see each email, role and Active or Deactivated status.
  2. Change the role in the list. For a self-service billed organization, a seat change is synchronized before it is accepted; if synchronization fails, the previous role is restored. Moving a member to Viewer also lowers their project shares to Viewer.
  3. Use Deactivate to end sessions immediately and prevent a new sign-in. Reactivate restores the account when seat rules allow it.
  4. To delete an account, select Delete and retype its email. Projects and the audit trail stay with the organization; the invitations the person sent, the ones addressed to them and their MCP tokens are erased. You cannot delete your own account from this page.
  5. Open Invitations → New invitation. Enter Email and Role, then, if needed, a Project (optional) and a Project role. For a Viewer, the project role can only be Viewer.
  6. Select Send the invitation. Follow its state: Pending, Accepted, Revoked or Expired. Resend replaces the previous link; Revoke makes it unusable.

Organization roles are Owner, Admin, Project manager, Editor and Viewer. Owner and Admin administer the organization and create projects; a project manager creates projects and sees every organization project; an editor creates projects and works on their own and on those shared with them; a viewer, a free seat, can only view the projects shared with them. Project roles are Viewer, Reviewer, Editor and Project admin. For the full matrix, see Members, roles and invitations.

Configure sessions, 2FA and Entra ID

UI path: Administration → Security.

  1. Select Require email 2FA for native sign-ins if every password sign-in must pass a six-digit email code.
  2. Enter Session lifetime (minutes) from 15 to 10,080 (seven days).
  3. Select Save and wait for Saved.

The new lifetime applies to new sessions; existing sessions expire normally. Deactivating a user, by contrast, revokes their session immediately. After an email code, a user can select Trust this device for 30 days; do not do so on shared or public workstations.

For Microsoft, open Microsoft Entra ID → Connect Microsoft, sign in as a Microsoft 365 administrator and accept the requested consent. PlanRelevé then asks for a sign-in with a member account of your organization's own Microsoft 365 tenant to confirm the link; a guest or partner (MSP/GDAP) account is refused. The page then shows Microsoft sign-in is connected and active. Ordinary members then use Microsoft; owners and admins keep native sign-in as a fallback. New Entra users join as Viewers until an administrator grants more access. If organization 2FA is required, Microsoft sign-in must report MFA. PlanRelevé refuses to disable Entra when no active owner or admin with a native password remains.

Do not treat enabling Entra or 2FA as proof of compliance on its own. Test with a non-administrator account and keep at least one administrator fallback before changing the policy. See Security, privacy and Law 25.

Monitor storage and retention

UI path: Administration → Storage.

The page shows Used, Included and Overage, then breaks bytes down by artefact type. Included storage is the base capacity plus any extra capacity granted to the organization. Where purchasing is available, Buy extra storage leads to checkout; see Subscription, seats, storage and AI.

Under File retention, Exports (days, empty = keep) sets after how many days the organization data exports (the ZIP files produced under Audit & data) are deleted; a daily job applies it. A value must be at least one day; blank means keep. Page renders have no setting: they are regenerated from the plan as needed and deleted with the project. This retention does not delete source PDFs, detections or the audit log, and saving it deletes nothing immediately.

For a full export or a deletion request, use Audit & data. Organization deletion follows a separate process; retention does not replace it. See Security, privacy and Law 25.

Configure taxes

UI path: Administration → Tax groups.

  1. Select Add group and name it.
  2. Add the lines in calculation order, each with a label (Tax) and Rate %.
  3. Select Compound only when a line must tax the taxes above it.
  4. Mark one group Default, then select Save.

An unconfigured organization receives the TPS + TVQ (Québec) group. A project uses the live organization default until a group is chosen on its Estimate page; that choice freezes the current labels and rates into that estimate, so a later organization edit does not silently change the quote. No tax is also available. Always verify the applicable rates, order and tax treatment with the person responsible; PlanRelevé does not provide tax advice. Details: Estimating, labour, margins and taxes.

Enable AI with two consents

The Artificial intelligence card shows the active tier and monthly usage as Input and Output percentages.

  1. Enable AI features permits AI features on structured data and typed text.
  2. Allow AI on plan/spec content is a second consent, required for any feature that sends document content to the inference provider, including a PDF or an image attached to the assistant.
  3. Enabling either one requires you to Accept the displayed terms.

The Included (1×) tier is provided to every organization, whatever its plan; AI 5× and AI 20× multiply that quota. Choose a tier, then Change: an upgrade applies immediately; a downgrade is scheduled for the paid period end and can be reversed before then with Undo change. This self-service change requires an active Stripe subscription; a manually billed organization goes through its account manager. The billing tier does not turn on the consents for you, and a consent can be withdrawn without changing tier. See AI assistant and approved actions and Subscription, seats, storage and AI.

MCP, audit and branding

The MCP server card shows Enabled or Disabled and opens activation and integration tokens. Enabling MCP and issuing tokens are separate administrator actions; AI consent does not enable MCP. Leave the server disabled if no external client needs it; scope and revocation details are in API and MCP integrations.

Under Audit & data, the Audit log filters events by type and email. Review it for role, invitation, AI, MCP and parts and assembly library changes, and for export requests. Data export & deletion produces a controlled copy of the organization's data.

Under Branding, update the Organization name and optionally upload a PNG/JPEG logo no larger than 512 KB, then select Save branding. Verify the name and logo in the application header; Remove logo restores the platform branding. Use only an authorized file that contains no sensitive information.

If a save fails, read the displayed error, reload the page to confirm the stored state and retry once; do not assume a checked box was persisted. For repeated authorization, identity or deletion failures, record the affected user, time and action without copying passwords, one-time codes or tokens into a support request.

See also