Invite a member
1
Open Members
Open Settings › Members. The People card shows who has access to this workspace, and at what privilege.
2
Enter the address and the role
Under Invite new members by email address, fill in Email Address and choose a Role: Read, Policy Writer, Admin or Owner. Click Add More to invite several people at once.
3
Send the invitation
Click Invite Member. The person gets an email and joins by signing in with that address. There is no link to forward. The invitation expires 14 days after it is sent.
4
Watch it land
The invitation sits under Pending Invitations until the person signs in. Then they appear under Team Members with the role you chose.
Manage access
The two tabs are Team Members and Pending Invitations. Use Filter…, All Roles and Date Added to find a row. Each row has Manage Role, Copy Email and, for an invitation, Revoke Invite… and a resend action. Removal is immediate in effect. The dashboard puts it this way: “Membership is re-read on every request, so a removal takes effect on the member’s next call.” The four roles are enforced server-side on every call, highest privilege first. Owner reaches everything an Admin does, and the last owner cannot be removed. Admin reaches everything a Policy Writer does. Policy Writer reaches everything a Read member does. Every member can read all workspace data. You can change or remove only members whose current role is at or below your own: an Admin can change or remove a Read member, a Policy Writer or another Admin. Only an Owner can change or remove an Owner, or revoke an invitation to the Owner role. The matrix What each role can do lists each action; see Roles and permissions.Feature visibility
Feature visibility decides which parts of the product the Read and Policy Writer roles can see. Admins and owners always see everything, so a change can always be undone. Untick a feature for a role and click Save. “Hidden features disappear from the navigation on the member’s next page load.” Every role can read this table. Only an Admin or Owner can change it: for the other roles the boxes and Save are disabled and the card reads “Admin only — your role can view this setting but not change it.”Sign-in, MFA and sessions
Settings › Security is read-only. It states how people sign in and what governs it.- Methods. Hosted SSO (WorkOS AuthKit) and Google. An email one-time code is the fallback: a 6-digit code that expires in 10 minutes.
- Access. Signing in requires a membership an admin created. “Access is granted by your workspace admin. There is no self-service signup.”
- MFA. Quint does not enforce MFA itself. It inherits whatever your identity provider enforces.
- Sessions. Sessions last one hour. A tab that is actively loading data renews silently; an idle tab does not.
- Removal. Membership is re-read from the database on every authenticated call, so a removed member is refused immediately.
- SCIM. Directory provisioning over SCIM does not exist yet.
- IP allowlisting. Not available.