Concepts#
Projects#
AEN users interact with the system predominantly through projects.
A project is a set of conda environments, Jupyter Notebooks, and other files.
Each project has a project drive that all team members can access. The size of the drive is not limited by AEN. Contact your system administrator if you find you do not have sufficient space.
Each project has a separate project directory on the project drive.
The project directory is a directory for project files and data that is separate from the project owner’s and team members’ home directories, so that team members can share and have equal access.
The path to your project directory is
/projects/<project_owner>/<project_name>.
For administrative information about projects, directories, and permissions, see Projects and permissions.
Team collaboration#
Teams collaborate in AEN using projects. Projects allow a team to easily come together by sharing the resources, applications, and environments that are necessary to collaborate effectively.
The AEN project owner and any team members connected to their project will have access to the same:
Shared files and home directories.
Shared Python and R environments.
Shared nodes and hardware.
Common applications.
Web user interface.
For more information, see Working with projects.
Access control#
AEN access controls allow you to:
Add and remove project access for new team members.
Limit the access to specific folders and files to members of your project team.
Use permissions to extend execute access to team members. By default, all of the team members on a project have read and write access to all project assets.
Access control is performed from each project’s Workbench application.
For more information, see Controlling access to your project.