Notion Guest vs Member: Access, Costs, and Client Invites

Use a Notion guest for a client or collaborator who needs selected pages. Use a member for someone who needs to work across your workspace, join teamspaces, or belong to permission groups. On paid plans, members add a seat charge; guests do not. The role decides how someone participates in the workspace. The permission you give them on each page decides whether they can read, comment, edit, or share it.

For a client reviewing a proposal, I recommend a guest invitation with Can comment. A contractor maintaining your internal projects, wiki, and team processes may need membership. A long contract alone is no reason to buy a seat: start with the content and actions the person needs.

What changes between a guest and a member?

Notion defines guests as page-by-page collaborators. You can invite the same guest to more than one page. Members join the workspace and can participate in its shared content, subject to page and teamspace permissions.

The practical distinction is access scope. A guest can edit a shared project page without becoming a workspace member. Making someone a member does not mean they should receive Full access to your project database.

Are guests free, and what do members cost?

Guests do not consume ordinary paid member seats. At the October 13, 2026 check, Notion's US pricing page showed the following guest allowances and member prices with USD and annual billing selected.

The Plus and Business figures are annual billing rates expressed per month. Use the billing selector and your workspace's actual offer before committing.

For example, three additional Plus members at that annual list price represent 3 × $10 × 12 = $360 per year in member-seat cost. Three guest reviewers add no member-seat charge. That comparison excludes taxes, discounts, other services, and any charge for upgrading the workspace itself. For your own role mix, the editable team cost worksheet (XLSX) separates guests from paid seats and shows annual commitments, monthly equivalents, and optional AI-credit costs.

Free has a separate collaboration limit: a workspace with more than one member can use up to 1,000 blocks. A freelancer inviting a client as a guest avoids adding a second member, but still needs to stay within the Free guest allowance.

There is a specific exception to ordinary member billing. Approved Notion Marketplace consultants can receive temporary membership without using a paid seat, with an expiration date set by an admin. This is not a general free-member option for every contractor.

Choose the role by the work, not the person's job title

Write down the pages someone needs and what they must do there. That short list is more useful than deciding that every freelancer is a guest or every long-term partner is a member.

• A client approving drafts: guest access to the client portal or proposal, usually with Can comment.
• A freelance designer delivering one project: guest access to its brief, assets, and agreed delivery pages. Give editing permission only where they need to change content.
• A teammate working across projects and the internal wiki: membership, with access organized through the relevant teamspaces or groups.
• An embedded contractor: membership may be appropriate if they need the same ongoing workspace participation as your team. Check which internal content becomes available before inviting them.

Notion's role-selection guide makes the same distinction between broad organizational work and specific shared projects. I would keep a returning client as a guest while their work stays within an explicit set of client-facing pages.

Notion also documents a restricted-member role. It requires explicit access to teamspaces and pages, supports capabilities such as permission groups and private pages, and affects billing like a regular member. If your workspace offers that role, consider it when someone needs member capabilities with a narrower access scope. It does not provide guest pricing.

Set page permissions separately

Once you choose guest or member, assign the permission the person needs for the task. Notion's page permission levels distinguish reading, commenting, editing, and sharing:

• Can view: read the page.
• Can comment: leave feedback without editing the content.
• Can edit: edit content without permission to share the page with other people.
• Can edit content: on a database, create and edit its pages and property values without changing the database structure, properties, views, sorts, or filters.
• Full access: edit content and share the page with others.

For a reviewer, Can comment is usually enough. For someone updating deliverables in a database, Can edit content can protect the database's structure. It does not, by itself, limit the person to a particular client's records.

Check the parent page before sending the invitation. Subpages inherit its permissions by default, and Notion applies the broadest access a person receives. A more restrictive individual setting cannot cancel a broader grant elsewhere. If you are sharing a client database, use the client portal permissions guide to review records, inherited access, and public links before handing over the portal.

How to invite someone as a guest

Use the page invitation flow for selected-page access, following Notion's documented guest invitation steps.

Before sending a new invitation, have someone who can manage workspace people check the intended email in the existing Members and Guests lists. Record any current access rather than assuming an external email means a new guest. Decide on the role first, then send the invitation from the right place.

1. Open the page you intend to share and select Share at the top right.
2. Enter the guest's email address.
3. Select the page permission they need, then select Invite.
4. If Notion offers to add them as a member, select Skip for now to keep the invitation as guest access.

The recipient gets an email link and needs a Notion account to access the privately shared page. They can sign up if they do not already have one.

After inviting them, confirm their role under Settings → People or Members, depending on your plan, then open Guests. Review the pages listed for that person. Check the shared page's permission level as well; appearing in the Guests tab confirms the role, not that every page permission is correct.

Ask the recipient to open the exact privately shared page while signed into the invited account. For a proposal reviewer, the intended outcome is reading and commenting without editing the proposal. If the page will not open, compare the invited address with the signed-in account and inspect that page’s grant before widening access. If they can edit unexpectedly, check their broader grants; changing only this invitation’s permission may not remove the wider access.

Why was someone added as a member instead?

A page invitation and a workspace invitation have different outcomes. A workspace invite link adds someone as a member; on a paid plan, that uses a paid seat. The Add members flow is also for membership. Do not send a client the workspace invitation link when your intention is guest access to one portal.

The same documentation describes two other paths worth checking:

• Allowed email domains: someone with an allowed domain can choose to join the workspace as a member during onboarding, with the corresponding billing effect.
• Guest limits and matching domains: when a workspace is above its guest limit, a new invitee whose email belongs to a workspace domain can be added only as a member. Notion's sharing documentation describes automatic member addition in this situation.

On Enterprise, guest-invitation policies can also affect how a page invite is handled. Notion advises hovering over the recipient's name or email before selecting Invite to see how they will be added. If the proposed role differs from the one you intended, stop and have the workspace owner review it.

If a guest invitation fails, check the current guest allowance, workspace or teamspace guest restrictions, and email-domain restrictions. Buying a member seat is not an automatic fix for a blocked client invitation: it changes both the role and, on paid plans, the bill.

Change or remove access deliberately

When a guest begins working across your team, a workspace owner or membership admin can upgrade the guest to a member from Settings → People or Members, depending on the plan, then Guests. Select the guest and the upgrade option. On paid plans, the additional member is charged as a seat, so approve the cost and review the workspace content they will gain access to before converting them.

To end access to one page, remove that person's grant in its Share menu and check whether another permission still gives them access. To end their workspace access, an owner or membership admin can remove them from the Members or Guests tab. This avoids treating removal from one portal page as complete offboarding.

Before removing a member, make sure work your team needs is shared with someone who will remain. Notion says removal immediately ends workspace access and hides the member's private pages. It also says rejoining within 30 days restores private and shared pages, group membership, and teamspace membership. If the person returns, review that restored access rather than assuming the invitation starts from an empty permission set.

For a client engagement, keep a short record of the guest's email, shared pages, permission levels, and access end date. It gives you a concrete list to review when the project closes or the client's responsibilities change.