Idea

Enforce Team Hub member role permissions on shared documents

Forum|Forum|16 days ago
September 22, 2026
5 replies
68 views

I’m finding situations where documents shared with a Team Hub allow permissions on the document that supersede an individual member’s roles.

For example, if a member outside the team hub shares a document with the team, they must provide a permission setting at the time the sharing is executed. Members of the team the document is being shared with has a mix of member roles, some that can edit, others that are view only. I am finding that if the document owner allows edit capabilities during the sharing process, these edit capabilities are applied to all members in the Team Hub and the member’s hub role is not enforced. This means members that should only have view capabilities now have edit privileges.

Another way to describe the flow: the project team is sharing a document with the development team. Some of the members of the development team have edit roles, others have view-only. However, in this case, because the project team document is shared with edit permissions, all members of the team can edit even though some should only have view.

Are we not sharing documents in the correct manner for this to work properly and inherit the Team Hub member role permissions? This works fine for documents created in the Team Hub, just not when documents are shared with a team.

Thank you.

Humas1985

Lucid Legend Level 10

Hi @zorg

It appears that the document-level permission applied during sharing may be granting edit access to all Team Hub members, rather than using each member’s hub role as a permission limit.

For mixed access, you may want to share the document with the appropriate users/groups at the required edit or view level, or manage the document directly within the Team Hub.

To learn more:

Share with collaborators in Lucid – Lucid

Use team hubs in Lucid to collaborate and stay organized – Lucid

Hope this helps !!

Huma || Lucid Legend

Z

zorgAuthor

Thank you for the response. The goal of using Teams is to eliminate the need for someone sharing to worry about a team’s access controls. Sharing with individuals destroys the purpose of having a team such that members come and go requiring someone to manage access at a document level, not at a team level.

If the only work around is to share individually, this gap should be raised to the product team to evaluate and fix to allow an enterprise sharing model to work at scale.

Thank you.

Leianne C

Lucid support team

Hi @zorg, thank you for posting in the community and apologies for the delayed response. Just wanted to add to the great resources @Humas1985 that shared - I was able to reproduce the described behaviour and am looking into this.

I will share an update here as soon as I have more details.

Please feel free to let us know if you have any additional questions or concerns in the meantime.

Leianne C

Lucid support team

Hi @zorg, thank you for your patience while I looked into this!

Our development team confirmed that this is expected behavior. Team membership permissions (like view-only) only apply to documents owned by the Team.

When an individual document is explicitly shared with the Team with edit permissions, those specific document permissions take precedence. As a result, any Team member with an active Lucid license will be able to edit that document.

That being said, I completely understand your point about how this impacts scaling an enterprise sharing model. While this isn’t currently supported, we’re very interested in your feedback and committed to continually improving Lucid.

I’ve converted this post into an Idea within the Product Feedback section of the community so that it's visible to our Product Team and other users can upvote it or add their own details. If you have any additional context about your ideal workflow, please feel free to reply directly in this thread!

For more details on how we process suggestions, you can check out this post:

Thank you again for sharing your feedback in the community!

Z

zorgAuthor

Thank you for following up.

This should really be addressed as it breaks various sharing and security models. The easy work around is the converse of what was mentioned earlier. Should a member on the team with whom the document is shared require additional access to a particular document, it can be directly shared with them, not just the team in general, with the proper permissions. Otherwise, the team permission structure should be enforced and overridden on a case-by-case basis.

Thank you again.

Create an account in the community

Log in to the community