The home project is a special DiveLine project used to organize user files. It is designed to be the project that all users start in when they connect to a DiveLine server from a client. When the home project feature is enabled, each user stores all their files in their own home directory within the home project.
In addition, if you define project aliases in the home project, you can grant users access to published content in other projects on the DiveLine server. If you use project aliases in the home project, make sure that you define access control on the target project, not the alias.
The home project automates new user access control settings, home directories, default file access, and storage for client applications. This ensures that each end user has access only to the content they should access. By consolidating all users' file storage in the separate home project, you do not have to worry about users accidentally changing other files within the data project.
Follow these overall steps to implement the home project feature:
- Set the home project on the Projects tab. See Setting the Home Project.
- Set the home directory and access pattern on the Users tab. See Setting the Home Directory Settings.
- Set aliases to the appropriate folders within other projects. See Setting Aliases in the Home Project.
- Create new users, leaving the DiveLine settings for Home Directory, DiveBook, and App Template to use the defaults, which are now set by the home project.
See Managing Users and User Edit Tabs.
- If required, retrofit existing users to use the home project defaults.
See Retrofitting Users for the Home Project.