Skip to main content
    SonomosSupport Center
    Main Site

    Plans, teams & roles

    My Team

    The admin's page: who's on the team, what everyone must protect, and how the whole team is doing. Three tabs, and the middle one is the one that matters.

    Available toTeams Admin

    My Team appears in your sidebar under an Admin heading, and only for admins. The page header names your organization and its seat count.

    The three My Team tabs
    TabFor
    MembersInviting people, assigning roles, removing seats.
    PoliciesThe protection rules every member's device must meet.
    Team reportsSend members a request to generate a report for a date range, and see whether it is pending or done. Members generate their own reports; no report content is sent to you.

    Members

    Three seats: one admin, one active member, one invitation outstanding.

    1. Invite member — by email address, or by verified domain so anyone with a company address can join.
    2. Role — Admin or Member. Admins can do everything on this page; members can't see it.
    3. Policy — which policy that person's device is receiving.
    4. Status — a green dot for active, amber for invited but not yet joined.
    Actions on the Members tab
    ActionEffect
    Invite memberSends an invitation. The seat shows as Invited until they accept.
    Resend inviteFor invitations that were missed or expired.
    Edit rolePromotes a member to admin or demotes an admin to member. There must always be at least one admin.
    RemoveFrees the seat. That person's app reverts to Free on next launch, keeping full protection and losing the org policy and full reports.
    Walkthrough

    Adding someone to the team

    Step 1 of 5

    1Open My Team. The Members tab lists everyone on the team with their role, the policy their device is receiving, and whether they've accepted yet.

    Read all 5 steps as text
    1. Open My Team. The Members tab lists everyone on the team with their role, the policy their device is receiving, and whether they've accepted yet.
    2. Click Invite member, at the top right of the card.
    3. Enter their work email — or set up a verified domain so anyone with a company address can join without a per-person invitation.
    4. The new seat appears as Invited, with an amber dot and a Resend invite action. They aren't consuming policy yet.
    5. When they install Locke and accept, the dot turns green and your policy lands on their device automatically. No configuration on their end, and nothing for you to send them.

    Policies

    The heart of the page. Everything you switch on here becomes a requirement on every member's device — members can protect more, but never less; see the rule that explains Teams for the full case.

    The three sub-tabs deliberately mirror the individual Controls page one for one. If you know how to configure your own protection, you already know how to configure the team's — the only difference is who it applies to.

    Required surfaces. A 'required' pill means members can't turn it off.

    1. The banner states the rule: everything on applies to every member automatically.
    2. Required surfaces, Required data types, and Scanning floor — the same three axes as personal Controls.
    3. A required pill marks a row that's locked on across the team.
    The three policy axes
    Sub-tabSetsMembers can
    Required surfacesThe AI sites and apps every member must have protected.Add their own surfaces. Not switch off a required one.
    Required data typesThe categories of sensitive data every member must detect, plus team-wide custom rules.Enable extra categories. Not disable a required one.
    Scanning floorThe minimum sensitivity, and the input types that must be scanned.Applied to every member device as you set it.

    Team custom rules

    Rules you define under Required data types are pushed to every member, so the whole team catches your organization's matter codes, project codenames, and client shorthand without anyone configuring anything. This is usually the highest-value thing on the page: the identifiers unique to your business are exactly the ones no built-in detector could know about.

    Team custom rules. Write once, and every member's device catches them.

    Choosing a scanning floor for a team

    Stricter floors catch more and produce more false alarms — and on a team, the false alarms land on other people, who'll route them to you. A workable sequence:

    1. Start the team at Balanced, the same default as an individual.
    2. Watch Team reports for a couple of weeks. Look for members whose detections cluster in one data type — that's usually a false-alarm pattern, not a risk pattern.
    3. Raise the floor to Strict only for regulated work where a miss costs more than an interruption.
    4. If you do go Strict, tell people, and tell them that a masked value blocking real work is a message to send you.

    Team reports

    You get unlimited full reports for your own device on the Reports page. To get members' reports, pick members, a privacy regime and a date range, and send a request. Each member gets a prompt and generates their own report; you see pending or done per member. Report content isn't transmitted to you. A member's report also lists the strictness setting history and any approved history clears.

    Team-wide figures on top, per-member rows below.

    1. Members scopes any report to everyone or to one person.
    2. Team values masked and Detected, not masked — the second number should be zero; anything else is worth investigating.
    3. Members policy-compliant — the proportion of devices actually meeting your policy.
    4. Per-member counts, with View for one person's detail.

    A sane rollout order

    1. Set up your own device first, on Free-equivalent settings, and use it for a few days. You'll write better policy having felt the false alarms yourself.
    2. Create the organization and verify your email domain.
    3. Write the policy: required surfaces for the AI tools your team actually uses, required data types for your regulatory exposure, and a Balanced floor to start.
    4. Add your team's custom rules — matter codes, codenames, internal identifiers. Test each in the Sandbox first.
    5. Invite a handful of people, not everyone. Watch Team reports for a week.
    6. Roll out to the rest, then check compliance weekly rather than daily.

    What your members will experience is covered in For team members — worth reading before you push your first policy, so you know what they'll see.