Access Control Policy

Who may use PersivX and the systems behind it, how they prove who they are, what each role may do, and how access is taken away.

Policy ownerPersiv Technology
Approved byHarsh Jain and Ankit Kumar
Effective from1 November 2026
ReviewedAt least once a year, and after any significant change or incident. Next review: 1 November 2027

Principles

  • One person, one account. Accounts are never shared, inside PersivX or on any system that runs it.
  • Least privilege. People get the narrowest role that lets them do their job, and lose it when the job changes.
  • The server decides. Every permission is checked by the PersivX server against the signed-in user. Nothing the browser sends about who the user is, or what they may do, is trusted.

Roles in PersivX

RoleWhat it allowsHow it is granted
ViewerOpen reports shared with them, use filters, save views, subscribeDefault licence for a new user
DeveloperAlso build and save reports and visuals, manage datasources, governance rules and uploadsDeveloper licence, set by an organization admin
Organization adminManage the organization's users, licences, groups and sharingNamed as the organization's admin
Instance adminManage the whole installation: organizations, communication channels, licenceThe INSTANCE_ADMIN_USERID server setting; changed only by editing the server's settings

On top of the role, every report, visual, datasource, folder, subscription and channel carries its own rights (view, use, admin, owner), checked by the server on every request. Users in one organization can't reach another organization's content by changing an id. AI features and the scheduler are separate licences an admin grants per user.

Signing In

  • Passwords must be at least 10 characters, contain letters and numbers, not contain the user's name, username or email, and not appear in a known data breach. They are stored only as salted bcrypt hashes.
  • Repeated failures pause sign-in: 10 failed attempts for an account, or 50 from one network address, within 15 minutes.
  • Two-step verification (an authenticator app code) is available to every user. Setting AUTH_MFA_REQUIRED_FOR_ADMINS makes it compulsory for admins.
  • Account setup and password reset links work once. A setup link expires after 7 days, a reset link after 30 minutes.
  • Single sign-on (OpenID Connect) is optional: off for the whole server unless SSO_ENABLED is set, and then off for each organization until its admin sets it up. It signs in only existing accounts, matched by an email address at a domain the organization has proved it owns with a DNS record, and checks the provider's signed token (issuer, audience, expiry and a single-use value) on every sign-in. An organization can require it, which turns off password sign-in for its members except the instance admin. SSO sign-ins get the same sessions, two-step verification (unless the organization trusts its provider's), audit records and alerts as password sign-ins.

Sessions

  • A session ends after 12 hours without activity, and after 7 days at most. With Remember me it lasts up to 30 days.
  • Sessions end immediately on every device when the user changes or resets their password, and within a minute when an admin blocks the user, reclaims their licence or resets their two-step verification. An administrator can end every session on the server at once (revoke_auth_tokens).
  • Headless report captures (scheduled deliveries, PDF export) use a separate token that lasts 30 minutes, is limited to one report address, can only view, and is cancelled when the capture finishes.
  • Programs that use the PersivX Data API sign in as an OAuth client, and each client acts as one named PersivX user with that user's rights.

Granting, Reviewing and Removing Access

These rules cover the customer accounts Persiv administers and all Persiv staff access.

  • Granting. Access is requested by email and approved by Harsh Jain or Ankit Kumar before it is given. The approval is kept as a record.
  • Review. Every 3 months, Harsh Jain and Ankit Kumar review who has admin roles in PersivX, instance-admin rights, and access to Persiv's servers, databases and cloud accounts, and removes anything no longer needed. The review and its result are recorded.
  • Leaving or changing role. Access is removed within 1 business day: the PersivX account is blocked (which ends its sessions), server and cloud access is removed, and shared secrets the person knew are changed. See Personnel & Acceptable Use.

Access to Production Servers

  • Only Harsh Jain and Ankit Kumar may sign in to servers, databases or cloud consoles that hold customer data.
  • That access requires two-step verification and is made with SSH keys or through the cloud provider's console. Passwords are never shared and never sent by chat or email.
  • Customer data is looked at only to deliver support or operate the service, and only with Harsh Jain or Ankit Kumar's approval, recorded by email.