Team Management

Team Management helps account owners control who can access Localith, what each teammate can work on, and which listings they can manage.

Overview

Use this page when you need to invite teammates, define the level of access they should have, or review how permissions are handled inside your Localith workspace.

This guide is intentionally focused on the roles and permissions we can confirm from current product-support sources. It should help you set up access safely without over-claiming controls that still need deeper product confirmation.

What the current roles cover

Based on the current support source, Localith supports two core access levels:

• Admin — full workspace access, including all features and all connected listings
• Editor — limited access based on the permissions and listing access you assign

Editors can be restricted to specific locations and can be allowed or denied access to actions such as:

• posting content
• responding to reviews
• generating reports
• editing business information

Before you invite teammates

Before you add people to the workspace, decide:

• who should have full administrative control
• which teammates only need access to a subset of listings
• which actions should stay restricted to managers or account owners

This keeps permissions clean as your workspace grows.

Typical team-management setup flow

Use this as the safe setup sequence based on the current product guidance:

1. Open the team or account-access area in Localith.
2. Add the teammate you want to invite.
3. Choose whether they should be an Admin or an Editor.
4. If they are an Editor, define which listings they can manage.
5. Turn the relevant permissions on or off for posting, replying, reporting, and business-info editing.
6. Save the user setup and verify the access level before you rely on it operationally.

When to use Admin vs Editor

Use Admin when a person needs full operational control across the workspace.

Use Editor when a teammate should work only on a controlled subset of locations or actions. This is often the safer default for distributed teams, agencies, or regional operators who should not have unrestricted account-wide access.

Tips and best practices

• Keep the number of Admins small and deliberate.
• Use Editor access for day-to-day operators whenever full account control is not necessary.
• Restrict users to the listings they actually manage if your workspace covers many locations.
• Re-check permissions when someone changes roles internally or starts handling a new group of locations.

Limits or edge cases

• Current source coverage confirms role direction and permission categories, but not every UI-level permission combination.
• Team member limits may depend on plan level. If you need account-level limits or billing context, see Plans & Pricing.
• If your workspace structure is complex, test a new user's access before rollout so they do not get too much or too little permission.

Common questions