- Will the user need access to standard company files or folders immediately?
- Are collaborations associated individually or through groups? If through a group association, are there any standard groups that the user should be added to?
- Should the user be assigned any tasks to complete?
- Would any instructional comments on any files be helpful?
New User Password Resets and Email ConfirmationYou may experience some errors when creating users and immediately trying to
take actions with that user through the API. For example, a common error to
receive is
user_email_confirmation_required or password_reset_required.
These kinds of errors may block some actions within the API, but you can
still add the user as a collaborator on folders, add the user to groups, etc.Sample Overview
In this scenario we’ll focus on provisioning a new , as there are very different considerations when provisioning Box App User accounts. We’ll start with solving the most repeatable aspects of provisioning a user’s account, creating a general folder and file structure that everyone will have on first login, using groups to control access to shared files and folders for users. To create the managed user account itself, see .Guide steps
This guide walks through the provisioning process in three steps:Create architecture skeleton
Create an
etc/skel folder structure owned by your application’s service
account to hold the default files and folders for every new user.Populate content
Copy the skeleton content into a new user’s root folder when the account is
created.
Setup shared folders
Create shared folders in the service account and use groups to control
each user’s level of access.