Share only to specific people
I have sensitive confidential informations of an object that I want to share only with my client : so a link publicly available doesn't comply with this because anyone with the link can get to the content.
I want to be able to manage WHO PRECISELY I share that object with, by specifying an email adress, and be able ton revoke that person from the sharing, so that the person ONLY has access to it.
Plus : this might push people into creating their capacities.io account !
3 Comments
Sign in to comment
I don't think the idea of pushing people into creating their own accounts is part of the plan. Cap is meant to be a place where people come in willingly and enjoy their experience. Walls to access are usually a big turn off if you've been on the internet for any amount of time.
Note: I'm not against the idea of controlling who can access your objects. I'm just against the pushing side of it.
A workaround: export it as pdf and perhaps password protect it using another tool.
Sharing in Capacities is currently link-based only, so restricting access to specific people by email is not supported. Shared objects are accessible to anyone with the link, and there is no per-person permission or revocation. Your use case aligns with more granular permissions that are planned but not yet available. You can read more about current sharing behavior here: https://docs.capacities.io/tutorials/sharing
This reply was written by the Capacities AI Assistant. Please note AI may make mistakes. If this response doesn't resolve your question or issue and the community can't help either, feel free to reach out to us at
Thanks Sly for the idea of exporting, it's good even though it lacks toggle functionality, which can become important when content gets long.
I'm not fond of insisting that people create their account either, so any other option is welcome.
Another idea could be to protect the page with a password : we send the password+link to the person we want to share the object with, and we can regenerate the password at will. Ideally, it would be relevant to manage a password per person, so that revoking password for someone wouldn't impact other passwords.