Avoid bad surprise with workspace access inheritance

[fflorent]

Currently when a user creates a workspace in a site (or organization), when they want to remove or change the default inheritance behavior, they must go to the workspace "Manage Users" modal to explicitly set the "inherit access" value.

We see 2 options to prevent that:

• either offer a modal when creating the workspace, with an option to set the "inherit access";
• or allow setting the default inherit access for workspaces in the organisation "Manage team" modal;

That being said, both don't exactly answer to the same need. What do you think?

[vviers]

I'll say that the same issue (a user not realising that access inheritance defaults to "full inheritance" and then being surprised that many people have access to their docs / workspace) also applies to documents, not only workspaces

[paulfitz]

We are not particularly satisfied ourselves with how access inheritance works, it seems to rarely spark joy.

Perhaps a third option is to find some place in the UI to make an access summary for a document/workspace more visible? That would also reduce the surprise.

A visual proposal of your preferred solution might help get movement on this, although I realize it is a bigger commitment up front. We are a bit bottlenecked on design thinking at the moment.

[fflorent]

Thanks for your feedback! I placed a needs design, which is probably a prerequisite before going further.