Skip to main content
Kira creates your account’s first logins. There is no sign-up. After that, an administrator on your team adds everyone else without asking Kira. Adding and removing people explains how.

Asking for it

Send Kira, for each person you need from the start: who they are, which environment they need, and which role they should start with. Include at least one administrator, who can then add the rest. Sandbox and production are separate, as they are for API credentials. Ask at the same time as your API credentials rather than afterwards. The people who will answer compliance requests usually are not the people integrating, and a request sitting unanswered because nobody has a login is the most avoidable delay in an onboarding.

Signing in

People sign in with their own identity, not with your API key. An API key belongs to your system. A dashboard login belongs to a person, and what they do is recorded against them. Never hand a colleague an API key as a substitute for dashboard access. It is not the same permission, and it removes the record of who did what.

What each person can do

Everyone signs in to the same account and reads the same information. What differs is what each person may do with it, and the role they hold decides that. An administrator on your team sets those roles, and can change one at any time without asking Kira.

Roles and permissions

The five roles, and what each one grants.