- Newest
- Most votes
- Most comments
Hello,
I would recommend to create the access for individuals. This way you can block access for individual users, e.g. if an employee of your supplier leaves the company. It also allows you to attribute log entries to the person that caused them.
You would start by collecting a list of email addresses of the people you want to invite to your work-docs deployment. This has be done by a Work-docs Administrator: https://docs.aws.amazon.com/workdocs/latest/adminguide/invite_user.html
If you assign these users the role "Guest users" no costs will be induced, but they can only view the data that you share with them. If you want them to commend / update / create files you need to grant them the "User" role, which is a payed user type (currently 5 USD/month): https://docs.aws.amazon.com/workdocs/latest/adminguide/users_ovw.html
After that I would recommend to create a folder structure by external party. On this level you can create the necessary permissions for the invited employees of that company. This will be inherited by every subfolder and file that you create: https://docs.aws.amazon.com/workdocs/latest/adminguide/permissions.html
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 4 years ago