Feature Request Update: Page Level Permissions

Product Feedback
21

Two doc-level settings for search that we could toggle off would solve most of my issues without having to implement any user-related filtering:

  • “Show hidden pages” - I pretty much never want these to be surfaced, they’re hidden for a reason. Sometimes I see people finding their way to back-of-house pages through this when there’s a view specifically intended for what they’re trying to do.
  • “Show table rows” - This is another way that people are getting into stuff they shouldn’t see(and personally, I think it clutters up search results so that I never really use search). It’s a ton of effort to make sure that people can’t see hidden columns this way via an unintended layout. Also, it’s redundant if people are able to search in the views that we want them going to anyways.

If we could turn those off, I think it would both make me feel a lot more comfortable about what data we are exposing, and would be a better experience. I’m sure malicious people familiar with a browser could find things, but our biggest problem is just people accidentally finding themselves in views that aren’t intended to be user-facing and getting confused.

Even if this were only at the org level it would be an instant massive win for us.

22

I agree – i try to provide a curated set of views and layouts, and when my users find their way to hidden pages, or see things in search, they get confused. And then a giant confusion ball is rolling around and I have to say “sorry, Coda doesn’t let me turn that off” and we pretend the confusion went away but it’s still there.

one of my workarounds on my hidden pages, is to use a filter on all the views so that “regular users” – people with a coda user not in a specific list – don’t see any of the rows. that is, in the table filter something like the following:

AdminUsers.Contains(User()).Not()

But it’s fraught; I have to remember to do it, and all it does is hide the rows on that page. The real problem is that they got there in the first place. And there are so many ways for them to end up there!

  • a notification teleports them there when they click on it
  • doc search
  • threedot-menu and “See this in Tablename”

I just can’t keep the content limited to what I think they should see, and it’s a real problem. And spinning up a doc for each user, is NOT scalable in any way. The real fix is what we’re talking about in this thread.