> ## Documentation Index
> Fetch the complete documentation index at: https://visitdocs.planpoint.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Members & access

> Invite teammates to your account, individual Visits or Property Maps without sharing your login.

Each teammate signs in with their own Planpoint Visit account. An invitation grants access only after the recipient opens the confirmation link and accepts it.

## Choose the access scope

| Scope | Where to manage it | What it includes |
| - | - | - |
| Account | **Members** in the workspace sidebar | All current and future Visits and Property Maps owned by that account. Members can also create new ones under that account. |
| Property | Open a Visit, then **Members** in its sidebar | Only that Visit. It does not grant access to the rest of the owner's account. |
| Property Map | Open a Property Map, then **Members** in its sidebar | Only that map and previews of its linked properties. It does not grant editing access to those properties. |

The owner and administrators for the selected scope can manage its members. Editors do not see its member-management controls.

## Roles

| Permission | Editor | Administrator | Owner |
| - | - | - | - |
| Edit content and settings in the granted scope | Yes | Yes | Yes |
| Manage leads and view analytics for a granted Visit | Yes, subject to the owner's plan | Yes, subject to the owner's plan | Yes, subject to the owner's plan |
| Invite members, change their roles and remove their access | No | Yes, within the granted scope | Yes |
| Delete a Visit or Property Map | No | No | Yes |
| Archive or restore a Visit | No | No | Yes |
| Allow public visitors to spend purchased AI credits | No | No | Yes |

An administrator of one Visit or map cannot grant access to the owner's whole account. An account administrator can manage membership across that account's Visits and maps.

> [!NOTE]
>
> Membership never grants access to the owner's billing, payment details, password or email settings, and it does not transfer ownership. Members use the owner's existing plan, Visit allowance and AI credits for shared resources; they cannot manage the owner's billing.

## Invite a teammate

**1. Open Members**

Choose **Members** in the workspace sidebar for account-wide access, or open a Visit or Property Map and choose **Members** in its sidebar for access to that entity only.

**2. Choose the recipient and role**

Enter the teammate's email address, select **Editor** or **Administrator**, and click **Invite member**.

**3. Wait for acceptance**

The member appears as **Pending** until they accept. They do not have access yet. Invitations expire after seven days.

![Screenshot placeholder: Invite and manage members](https://mintcdn.com/planpoint-visit/Ejq3McKWK25K_TO2/images/account/members-placeholder.svg?fit=max\&auto=format\&n=Ejq3McKWK25K_TO2\&q=85\&s=8a7eada8b910aa19eacd7010c9d4b623)

Inviting teammates and managing their access

If email delivery fails, the pending invitation remains visible and the page reports the failure. Use **Resend invitation** after delivery is available. Resending replaces the old confirmation link, so the recipient must use the newest email.

## Accept an invitation

1. Open the confirmation link in the invitation email.
2. Sign in with the invited email address, or create a Planpoint Visit account with that address and complete signup verification. Continue in the same browser tab.
3. Open **Members** if you land on the dashboard, then click **Accept invitation**.

![Screenshot placeholder: Accept invitation](https://mintcdn.com/planpoint-visit/Ejq3McKWK25K_TO2/images/account/members-placeholder.svg?fit=max\&auto=format\&n=Ejq3McKWK25K_TO2\&q=85\&s=8a7eada8b910aa19eacd7010c9d4b623)

Accepting an invitation while signed in as the invited teammate

Simply signing in with a matching email is not enough: you must also open the confirmation link from the mailbox. If acceptance requires email confirmation, reopen the latest invitation email in the same tab.

Accepted resources appear under **Shared with me** on the Members page and in the relevant Properties or Property Maps lists. Use **Open** to enter the shared resource. Use **Decline** to reject an invitation without receiving access.

![Screenshot placeholder: Shared resources](https://mintcdn.com/planpoint-visit/Ejq3McKWK25K_TO2/images/account/members-placeholder.svg?fit=max\&auto=format\&n=Ejq3McKWK25K_TO2\&q=85\&s=8a7eada8b910aa19eacd7010c9d4b623)

Accepted memberships under Shared with me

## Create under a shared account

With an accepted account membership, open **Properties** or **Property Maps**, choose the owner in the **Account** selector, and create the new item. It belongs to that owner and uses their allowance, not your personal account's allowance.

> [!NOTE]
>
> The dashboard home page's **New property** action still creates in your own account. Use the Properties page and its Account selector when creating for a shared account.

## Direct and inherited access

On a Visit or map's Members page, **Account access** lists members whose access comes from the owner's account. Those inherited grants cannot be removed from the individual entity's page; manage them from the account's Members page.

Account and direct entity grants are independent. A member with both keeps access if you remove only one grant. The highest applicable role takes precedence, so lowering a direct grant to Editor does not override an inherited Administrator role.

## Property Map boundaries

A map-only member can edit the map and see previews of properties already linked to it, but cannot edit those Visits or drag their saved location pins without separate property or account access.

Newly added properties must belong to the map owner and must be accessible to the member adding them. Existing linked properties can remain on the map without a separate property-editing grant. See [Property Maps](https://visitdocs.planpoint.io/features/property-maps.md) for the map editor workflow.

## Change or remove access

* Change a direct member's role using the role selector on the relevant Members page.
* Use **Cancel invitation** to revoke a pending invitation, or **Remove member** to revoke an accepted grant.
* Members can use **Leave access** under Shared with me to give up their own grant.

Changes take effect on the next API request, including saves in an already-open editor. Removing one grant does not remove access inherited from another grant. To revoke all access to an entity, remove every applicable account and direct grant.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.