Teams, roles, and least privilege

Organization roles

• Owner: organization control and ownership-sensitive actions.
• Admin: broad operational administration without ownership transfer.
• Developer: database and development workflows permitted by policy.
• Billing: plans, invoices, and payment workflows.
• Viewer: read-only operational visibility.

Database roles

Database roles are separate from organization membership. Open Console → Database roles to create a login identity or reusable permission group for one database.

• Choose Connect only, Read only, or Read and write instead of granting privileges manually.
• Set connection limits and optional expiry dates for temporary integrations.
• Credentials are encrypted and displayed once; rotation invalidates the previous password immediately.
• Last active means the latest connection Renviq observed for that identity.
• A drift warning means the managed role is missing from PostgreSQL and should be investigated before reuse.

Invite a teammate

1. 1Open Team and enter the person’s work email.
2. 2Choose the least-privileged role that fits the job.
3. 3The recipient opens the secure invitation, signs in or creates the matching user account, verifies email, and enables required 2FA.
4. 4Review the member list after acceptance.

Platform administrators

Site operators are separate from customer organization roles. The platform owner can invite scoped operators for support, operations, security, billing, or other responsibilities. Operator actions require business reasons and are audited.