Sorry, we don't support your browser.  Install a modern browser
This post is closed.

Password protect individual pages in a public workspace#58

some pages might have sensitive data but most are OK for public viewing

4 years ago
1
Changed the status to
In Progress
3 years ago
1

If a user belongs to an internal group, they would have access to that page without a password. If someone is not in that group, they would need a password. This would be great.

3 years ago
2

More coloring on my use case:

  1. Although the page is in a public collection, it is restricted only to those who are on my team (Users?), so the public cannot see them.

  2. Although the page is in an internal, non public collection, my team of Users do not have access, but I give Guests access to just those pages. An example are Investor Updates: they should be under Finance, but not internally available, or Customer Specific pages, where we invite customers to look at pages that only concern them.

3 years ago
1

We’d love this too, use-case for us would be to have API reference documents, but some of the API endpoints are not available for public use so we’d want to only show them internally

2 years ago
1

I like something like this feature to have “private pages” while we have features that are not ready to go live yet, so we can work on them. Currently, if you have to make another doc change, then you have to publish everything (including any WIP).

2 years ago
1

Is the plan just to password protect pages? Or could it be applied to a section within a page?

2 years ago

We have added some new functionality to Archbee. Currently we can password protect/give guest access/magic links. This allows you to give selective access to a space. You can also use the DRAFT feature to keep specific pages from a space unpublished when the rest of the space is published. I ll close this feature request as it can reffer to a lot of use cases and you can propose new, specific use cases that we can consider for implementation

a year ago
Changed the status to
Completed
a year ago

We might have different external personas. We have external admins or those with higher privilege. They are not internal users. But the content is not generally available.

a year ago

Hi Timothy. At the moment we are not planning on having selective logins/auths on the public docs. A space will have the same visibility to all personas with access to it. The workaround is to have different spaces for your public content and this way you can select who can view them. If you have common content in these spaces, you can use Content Snippets and this way you will only write the content once and use it in multiple spaces.

a year ago