Zaysa

Teams and integrations

Built for the whole team.

Decide exactly what each person may do, on which cloud accounts, and check it before anyone tries. Connect the tools you already use and automate with API keys.

Start freeBook a demo
freeIncluded in Free

Community support

proOn the Pro plan

Slack integration, API keys, Email support

businessOn the Business plan

Priority support

What you are seeing
  1. 01Everyone with a role: Owner, Admin, Member or Viewer, plus your own policies
  2. 02Invite a new member
Members
4 roles
OWowner@company.comOwner

Example data.

Teams and integrations

IAM: roles, policies and teams

Also here: IAM

Add people and choose their access in one step: a role (Owner, Admin, Member or Viewer), teams, and the cloud accounts they see. It applies the moment they accept. Add ready-made roles such as Developer or FinOps, or write your own policies, and give them to a whole team at once or make an exception for one person. Limit anyone to the cloud accounts they work on. A Deny always wins over an Allow.

EXAMPLE
OwnerAdminMemberViewer

Plus your own policies and teams

Check access before anyone tries

Check access tells you whether a person may do something, on which cloud account, and names the role or policy that decides. Every page, every API key and the AI assistant follow the same rules, and every change to access is recorded.

EXAMPLE
Priya, run deployments, Google CloudAllowed
Priya, run deployments, AWSBlocked

Names the role or policy that decides

Two people for every deployment

Deployments belong to the organization, not to the person who made them. Every run stops after the plan and waits until someone else who may run deployments on that account approves it.

EXAMPLE
Run pressed by SamPlan ready
Approved by AlexApplied

Integrations

Also here: Connectors

On the Pro plan

The Connectors hub keeps cloud accounts, GitHub, Slack, Jenkins, Kubernetes, secrets and notification channels in one place.

EXAMPLE
githubConnected
slackConnected
jenkinsConnected
kubernetesConnected

API keys

Also here: API Keys

On the Pro plan

Create named API keys with only the permissions each integration needs. A key never does more than the person who made it may do right now, so removing someone takes their keys with them.

EXAMPLE
••••••••3f9a   Read and write
••••••••71c2   Read only

Plans and billing

Also here: Billing

Your plan, seats and invoices in one place. Upgrade, change or cancel anytime.

EXAMPLE
PlanPro, monthly
Seats3
InvoicesIn billing

Settings and sign-in security

Your profile, sign-in security with two-factor authentication, plan and email preferences.

EXAMPLE
Two-factor authenticationOn
Email preferencesYours to choose

Support

Included in Free

Documentation for every area, community support on Free, email support on Pro and priority support on Business.

EXAMPLE
CommunityFree
EmailPro
PriorityBusiness

More in Zaysa

Inventory and Cloud MapKnow exactly what you run, in every cloud.Cost and wasteStop paying for what you don't use.AutopilotFind the problem. Fix it with your approval.Kubernetes and VMsYour clusters and servers, next to your cloud.AccessGive access only when it's needed.CI/CD and TerraformShip infrastructure changes with a plan and an approval.

See what you run, and what it costs.

Free plan, no card needed.

Start freeBook a demo
Teams and integrations | Zaysa