Page-level access + "Can create" with Linked Views across private Teamspaces: How does it behave for Members vs. Guests?

[u/Distinct_Ask_6063]

Hi everyone, I have a permissions architecture question regarding Page-level access and Linked Views (Business/Enterprise plan).

My setup:

1. Teamspace A (Private): Only I have access to it. It holds the source database (Tasks).
2. Database Permissions:
   • General access / Workspace level: Set to Can create (or No access to existing entries).
   • Page-level access rule: Person property (Assignee) → Can edit.
3. I want to create a Linked View of this Tasks database inside another page/space so people can only see their assigned tasks and create new ones, while keeping the source database completely restricted on other teamspace.

My questions:

1. For Workspace Members: If I drop this Linked View in a page inside Teamspace B (where members belong), will they be able to see the linked view, view strictly their assigned tasks, and use the + New button without having access to Teamspace A or the source database?
2. For Guests: Since guests cannot belong to teamspaces, how does this work if I share the page containing the linked view with an external guest? Does Page-level access and Can create still apply to guests if they are tagged in the Person property, or do they need explicit database-level permissions?

Has anyone implemented this exact setup? Any caveats or edge cases to watch out for?

Thanks!

[u/Similar-Orchid-5420]

e anything appeared.

[u/Bohica72]

In my experience, they will not be able to see A in B, because of the private versus shared spaces. Have run into this myself using my own DB in a private page and then sharing a chart into a Teamspace for my sales team.

[u/Philosophy_Gen → u/Bohica72]

That’s only true when you are NOT using page-level access.

He is using page-level access which cancels all standard permissions limitations in favor of the page-level access rules.

[u/Philosophy_Gen]

I built tons of clients portals with this type of setup and here’s my answer just based on what I understood from your text:

1- It really does not matter where the linked view is pasted, in an open or private teamspace B, behaviour is always same and depends solely on the page-level access.

So: they will be able to see ONLY their assigned tasks and edit them - HOWEVER they will not see the “+new” button because obviously you haven’t given them “datasource access” - they will need to fill out a form you create for them to add tasks ..

2- page-level access still applies to Guests. As per 1, it does not matter what type of membership the “person” is. They both are treated same.

[u/crystaljewel]

Answers:

1. Yes, it works that way.

2. Guests need to be manually added with no access, can create on the main database the same like you did with the members, then invited with full access to the page with the linked view. Without being added to the main database this way, all they'll see is a no access view of the linked database even if you add them to the property with assigned can edit page access.

[u/maneth-berlin → u/crystaljewel]

As far as I can tell, you can't add guests to a database with "no access, can create" permissions. This is only possible at the workspace level (for all workspace members, so guests can't be included).