Security
Access & Permissions
Who can see and do what — organizations, roles, permissions, provider access, and approval authority.
The access model
Access in Infraova is organized around roles. Every team member in your organization has a role that determines what they can see and what actions they can take. Roles are assigned at the organization level. The role system is designed so that approval authority — the ability to approve infrastructure changes — is explicitly controlled and auditable.
Roles
Infraova has three roles. Owners have full access to everything in the organization — settings, connections, approvals, billing, team management, and API keys. Administrators have the same operational access as owners but cannot manage billing or delete the organization. Members have access to monitoring, issues, and reporting for the domains within their scope, but cannot manage connections, settings, or team members.
Approval authority
Approving infrastructure changes is a specific permission that is granted to owners and administrators by default. Members do not have approval authority unless it is explicitly granted. Approval authority can be scoped — a member can be granted approval authority for a specific client or set of domains without granting organization-wide approval rights. This allows agencies to give client-specific operators approval authority without elevated access to the full organization.
Note
Every approval is recorded with the approving operator's identity. Approval authority cannot be delegated — you cannot approve on behalf of someone else.
Provider connection access
Provider connections are managed by owners and administrators. Members cannot add, edit, or remove connections. This means the infrastructure access credentials — API keys and OAuth tokens for DNS providers and email platforms — are only accessible to operators with elevated roles. Members can see which providers are connected but cannot view or modify the credentials.
Inviting team members
Team members are invited by email from Settings → Team. The invitation specifies the role and, for members, any client or domain scope restrictions. Invitations expire after 7 days. An invited member must accept the invitation before they can access the organization. Pending invitations are visible in the team settings and can be revoked before acceptance.
Revoking access
Access can be revoked at any time from Settings → Team. Revoking access immediately terminates the team member's session and removes their ability to log in to the organization. Their historical actions remain in the audit trail — revocation does not delete the record of what they did while they had access.