As B2B company we would like to share our private documentation with 3rd party clients that have no access to Gitbook and provide them temporary access to documentation. This feature was available in legacy version (as access-keys). Alternatively provide an option to share the book by email to 3rd party that will be able to login seamlessly with basic login. Unlisted feature is partially provide solution for this request since it is not possible to revoke access from specific client.
@Samy Pessé Thanks for adding this. It is very helpful. Will be great to have next feature that will allow to generate and revoke link per client. So option to generate multiple sharable links to the same book. Also ability to share specific pages from a book under access link when we don't want to expose all the pages as part of the book to our clients
Ping
We've just released Shareable Links. Using shareable links, you can generate secret link for your private content.
You can find more infos in our blog article (https://medium.com/gitbook/shareable-links-happiness-is-only-real-when-shared-privately-5299ea8d9d76) or documentation (https://docs.gitbook.com/audience/private-sharing-link)
password protected read only view needed
@Aaron O'Mullan Any update here?
InvisionApp has a good implementation of this I think.
hy
Hi Everyone,
We're currently gathering feedback to help understand your different use-cases and requirements for private sharing.
So that we can find the right balance between simplicity & security to solve your needs.
If you haven't already, you can help us by filling out this form: https://docs.google.com/forms/d/e/1FAIpQLSdERO-jSizVhhD-L7jYhDxNLopiwl-Xop-7X17xMGPOPZ8CmA/viewform
@Aaron O'Mullan: Any update here?
@Aaron O'Mullan: Any update here?
The notebook should be private but its purpose is to be readed by an entire company so it would be great if we could add unlimited readers or add X access based on IP for example. (Like AWS VPN connections)
When you launch the new version of GitBook, make sure that the old access key links we provide our customers with still work and point to the legacy version of GitBook.
I'm talking about these links:
https://www.gitbook.com/read/book/my-org/my-book?key=somekey
Thank you!
Carl Mathisen
The legacy API had a great feature of key-based access which permits inviting external users to read private books. This, or something similar like one-time passwords would be great to invite external users.
Note, since SSO cannot be used for external users and manually managing a set of external read-accounts quickly becomes a non-option.
This issue is blocking us from becoming a paying customer. Implementation-wise this seems fairly simple and would be a great differentiator for some paid plans which there are exceedingly few of.
Hi @Maxim Fainshtein,
In the new version you can create a team (ex: "My customers") that can only access a specific space (https://docs.gitbook.com/organization-management/setting-up-permissions).
Then you can send by email an invite link to this specific team to your customers. They will have access to your private content.
You can revoke the invitation link, or revoke access from one of these customer easily from the UI.
We are working on improvements to the team feature to make this workflow easier to setup.
@Samy Pessé: Thanks. Is the invite to the external clients of ours requires additional payment, are those counted as additional users. It will be not useful if we would need to pay to users that are potential clients and to have negative ROI.
We noticed users have different privacy/security requirements:
- Some customers wanted it to be easily accessible, but not publicly accessible or indexed by Google
- Others have strong security requirements to protect sensitive content
So we're solving this problem of private sharing in two steps:
1. Allowing projects to be unlisted (so public, unlisted or private).
2. Improving our teams feature so you can connect a project to your custom auth layer / backend
The unlisted feature is merged into master and will be going live later today
We also had that problem. So I just build a docker image that allows a similar functionality.
FROM billryan/gitbook:base
RUN gitbook fetch latest
ADD . /book/
RUN gitbook install /book/
RUN gitbook build /book/
FROM golang
RUN go get github.com/gitu/protected
ADD keys.toml .
COPY --from=0 /book/_book /book/
EXPOSE 3000
CMD protected -keys keys.toml -serving /book
you'd have to add a keys.yaml file in the format:
"SECRET"="NAME"
and also add a this file to your .bookignore file.
voila you now have a docker file ablto serve your gitbook on 3000
@Samy Pessé It would be great if you could generate and revoke 'Private Sharing' links per client. And ever better if this could be done with an HTTP API that's in your roadmap as Planned now.