This is where your people live: who is in your organization, what they can do, and which team they belong to.

Open your organization settings. If you do not have permission, Cloneable says so plainly rather than showing you an empty page.

These are two separate permissions, and it surprises people.

Cloneable can allow somebody to open this page and see everyone, while none of the invite, edit or deactivate controls appear for them. That is deliberate rather than broken: it lets you give somebody visibility of your workforce without giving them the ability to change it.

So "I can see everyone but there are no buttons" is a working state, not a fault.

This is the most useful thing on the page and the easiest to miss.

You can filter the roster to just the people who need something doing about them:

Run through that filter before a job starts rather than after. Every one of those is cheaper to fix at the yard than at a pole.

The roster also shows each person's role, team, status, app version, when they were last seen, and their phone number, and you can search it by name.

One at a time, giving an email address, a role, and optionally a team. Cloneable marks the recommended role.

Or in bulk, by pasting a list. It accepts plain email addresses, an address with a role after it, or a spreadsheet export with email, role and team columns. You get a preview of what it is about to do before it does it, which is worth reading.

You can also set one role and one team to apply to everybody in the batch.

Choose the role deliberately. See Roles, and what each one can do.

An invited person who has not accepted shows as pending, and you can resend or cancel from their row.

Resend switches itself off after you have used it. The option grays out for that person and its label changes to "Invite resent", so grayed out with that label means Cloneable has already sent it, whether or not it reached them. Reloading the page makes it available again, but if the invite still has not landed, chase them another way rather than assuming it failed to send.

Deactivating takes away their access. Cloneable explains exactly what that means, and it is worth reading because it is more reassuring than it sounds:

On screen: "This revokes their access to the organization. They will still appear for reference on resources they were associated with, and you can add them back at any time."

So historic work stays attributed to them, and this is reversible. It is the right action when somebody leaves, rather than something to avoid.

Teams group your people the way groups organize your jobs. You create them on their own tab.

Create your teams before you invite in bulk, because the invite screen can put people straight into one, and until a team exists there is no team for it to offer.

This lives on the same page as your people, and it applies to your whole organization at once.

Enable field location sharing is the master switch. Cloneable's own wording:

On screen: "When off, no location is shared or stored, and field users won't appear on the map."

Background location during work hours keeps positions up to date while the app is not in front of somebody, within hours you set. Those hours use each device's own local time, which matters if you work across time zones.

You cannot turn on the background setting while the master switch is off. If you try to enable it and it will not respond, check the master switch first.

Only organization admins can change these. Others with access to this page can read the policy but not alter it.

For what this changes on the map, see Your organization map.