Applies to: All customers.
In this guide
Who: Org Admin.
Adding people is one of the first things you will do, and it can happen any time, including while you wait for Cloneable to wire up your trigger.
Every person you invite gets one of the five roles in the roles table in the roles and permissions appendix (the full per-task grid is in the Appendix and reference). Most people should be Analyst / Fielder, which is the recommended default and is the role that can collect and manage data. Reserve Org Admin for the small number of people who administer the whole organization.
How to invite someone
Open Settings, then Organization, then the Users area.
Click Invite Users.
Enter one or more email addresses.
Pick a role. The default is Analyst / Fielder, which is marked as recommended.
Optionally assign the person to a team.
Click Send Invites.
The people you invite receive an email invitation and sign in the same way everyone does (see how you sign in, in Start here): with a one-time code, or through your company single sign-on if it is set up. There is no password to create.
Invitations you have sent but that have not been accepted show up under a Pending filter, where you can Resend or Cancel them.
Removing or changing people
Deactivate a user from the Users table. This revokes their organization-wide access and is reversible (you can re-add them). Removing a member from a single team is a separate action on that team's page.
Change someone's role from the same place. Changing roles is an Org Admin action.
Team Admin is a defined role, and a team's detail page does let its members be invited (choosing User or Team Admin at invite time) and removed. There is no control to change an existing member's team role; remove and re-invite them instead. There is no menu path for a Team Admin today. In the current portal the Teams area is reached only through the Org-Admin-gated Organization page, so a Team Admin has no menu path of their own to get there; today an Org Admin opens team management. If you want someone managing a team directly, give them Org Admin or ask Cloneable.
Deactivating a user who has left revokes their access (they can be re-added later). Seat and plan limits are handled by Cloneable rather than shown in the portal, so if you need more seats, talk to your Cloneable contact.
Teams
A team is a named group of people, useful for organizing crews within a larger organization. Assign users to a team when you invite them, or from the team's page later.
Single sign-on
Cloneable supports company single sign-on, but it is set up by Cloneable rather than turned on by you in Settings. If your organization wants single sign-on, give your Cloneable contact your identity provider details and Cloneable will configure it. Once it is on, your people can sign in with it instead of the email code. Day to day, if single sign-on is not set up, everyone signs in with the one-time email code.
A note on programmatic access keys
Cloneable also has API keys, which let outside systems make requests into the Cloneable platform. These are a different thing from the secrets vault (which stores credentials Cloneable uses to reach out to Katapult on your behalf). In the current portal, API keys are managed by Cloneable. If you have a use case for programmatic access, raise it with your Cloneable contact.
What an invited person does
The first time an invited person opens Cloneable or UtilityScout, they complete a short one-time profile step: they enter their first and last name and choose Sign Up to finish joining your organization. This is expected, not an error. After that, they sign in the same way everyone does, with a one-time code sent to their email.