Use this when a contributor should sign in to BaseBuddy and work only on posts assigned to their own mapped author record.

BaseBuddy cannot infer ownership from local BaseBuddy auth, the member's email address, or an author email field alone. The saved post-author mapping is required. BaseBuddy needs to know which author record belongs to the member and which posts point to that author record.

If you are still deciding whether this person needs an author record, a member account, or both, start with Authors vs members: what is the difference?.

Before you start

Make sure your posts and authors are mapped first.

1. Open the project.
2. Open Project Settings.
3. Open Mapping.
4. Confirm Posts mapping is saved.
5. Confirm Authors mapping is saved.
6. Open a known post and check that the sidebar shows the correct Author.

If the wrong author appears, fix the mapping before changing member access. Author-scoped permissions use the saved author relation, so a bad relation means the wrong posts may be included or excluded.

Use How to map authors to posts on BaseBuddy or How to set up authors on BaseBuddy if author mapping is not ready yet.

Choose the right access shape

For own-post access, use the Author role with one or more Author scopes.

Do not combine Author with all-content roles when the goal is only that user's own posts. In the default roles, Viewer can read all content, Editor can read and edit all content, and Admin or Owner can manage much more than authored content.

Use this pattern instead:

For the full role matrix, see Permissions and roles: how BaseBuddy handles them.

Update an existing member

Use this flow when the person is already a project member.

1. Open the project.
2. Select Project Settings in the sidebar.
3. Open Members.
4. Find the member.
5. Select Manage access.
6. Under Roles, select Author.
7. Remove all-content roles such as Viewer, Editor, Admin, or Owner unless the user should keep broader access.
8. Under Author scopes, select the author record that belongs to this user.
9. Use the Publish switch for that author only if the user should publish, unpublish, archive, or save mapped status changes for their posts.
10. Select Save access.

Changes apply only after you select Save access for that member.

If no author options appear, BaseBuddy does not have usable author records for this project yet. Recheck the saved author mapping and confirm at least one post shows the expected Author in the editor.

For a narrower version of this flow, see How to assign author scope to a member.

Invite a new user with own-post access

Use this flow when the person is not a member yet.

1. Open the project.
2. Select Project Settings in the sidebar.
3. Open Invite Members.
4. Enter the user's email address.
5. Under Roles, select Author.
6. Do not select all-content roles such as Viewer or Editor if the goal is only own-post access.
7. Under Author scopes, select the mapped author record for that user.
8. Turn Publish on only if this user should publish for that author.
9. Select Create invite link.
10. Share the copied invite link through your team's trusted channel.

Invitees must sign in with the same email address used on the invite. For the full invite flow, see How to invite users to your BaseBuddy project.

How read, edit, and publish are limited

BaseBuddy checks both permissions and the mapped post-author relation.

If the Publish switch is off for an author scope, the member may still read and edit posts for that author, but they cannot publish, unpublish, archive, or save a mapped status change for those posts.

Posts without a mapped author, posts assigned to another author, or posts whose author relation is unsupported for access checks should not be treated as the user's own posts. Fix the saved mapping before relying on author-scoped access.

Verify the result

Test with the affected user or a test account that has the same role and author scope.

1. Choose one post assigned to the user's mapped author record.
2. Choose another post assigned to a different author, or a post with no mapped author.
3. Sign in as the user.
4. Confirm the assigned post is available.
5. Open the assigned post and make a small safe edit.
6. Select Save and confirm the edit succeeds.
7. Confirm the unassigned or different-author post is not available, or cannot be opened or edited.
8. If Publish is on, test Publish, Unpublish, Archive, and one normal save that changes mapped status.
9. If Publish is off, confirm those publish and status-change actions are blocked.

If the user can see too much, check whether they also have Viewer, Editor, Admin, Owner, or an explicit all-content permission.

If the user cannot see the assigned post, check the saved author mapping first, then check the member's Author role, selected Author scopes, the Publish switch, and any permission overrides.

What this does not cover

This page does not set up Supabase Row Level Security, change your content schema, create a new authors table, or sync local BaseBuddy auth users to author records.

It also does not promise automatic ownership detection from email fields. Email can help your team recognize a person, but BaseBuddy uses the saved post-author mapping and the member's author scopes for authored access.

Related guides

• How to map authors to posts on BaseBuddy
• How to set up authors on BaseBuddy
• How to assign author scope to a member
• Authors vs members: what is the difference?
• Permissions and roles: how BaseBuddy handles them
• How to invite users to your BaseBuddy project
• How to customize permissions on BaseBuddy

Related pages

• Permissions and teams
• Permissions and roles: how BaseBuddy handles them
• How to check what a member can access
• How to customize permissions on BaseBuddy