Concepts (AEN 4.2.0)
====================

.. raw:: html

    <div class="contents local topic" id="contents">
    <ul class="simple">
    <li><a class="reference internal" href="#projects" id="id1">Projects</a></li>
    <li><a class="reference internal" href="#team-collaboration" id="id2">Team collaboration</a></li>
    <li><a class="reference internal" href="#access-control" id="id3">Access control</a></li>
    <li><a class="reference internal" href="#sharing-projects" id="id4">Sharing projects</a></li>
    <li><a class="reference internal" href="#project-tags" id="id5">Project tags</a></li>
    </ul>
    </div>
    <div class="section" id="projects">
    <span id="user-concept-projects"></span><h2><a class="toc-backref" href="#id1">Projects</a><a class="headerlink" href="#projects" title="Permalink to this headline">¶</a></h2>
    <p>AEN users interact with the system predominantly through projects.</p>
    <p>A project is a set of conda environments, Jupyter Notebooks, and
    other files.</p>
    <p>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 sufficent
    space.</p>
    <p>Each project has a separate project directory on the project
    drive.</p>
    <p>The project directory is a directory for project files and data
    that is separate from the project owner&#8217;s and team members&#8217; home
    directories, so that team members can share and have equal access.</p>
    <p>The path to your project directory is
    <code class="docutils literal"><span class="pre">/projects/&lt;project_owner&gt;/&lt;project_name&gt;</span></code>.</p>
    <p>For administrative information about projects, directories, and
    permissions, see <a class="reference internal" href="../admin-guide/concepts.html#admin-concept-projects-permissions"><span class="std std-ref">Projects and permissions</span></a>.</p>
    </div>
    <div class="section" id="team-collaboration">
    <span id="user-concept-team"></span><h2><a class="toc-backref" href="#id2">Team collaboration</a><a class="headerlink" href="#team-collaboration" title="Permalink to this headline">¶</a></h2>
    <p>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.</p>
    <p>The AEN project owner and any team members connected to their
    project will have access to the same:</p>
    <ul class="simple">
    <li>Shared files and home directories.</li>
    <li>Shared Python and R environments.</li>
    <li>Shared nodes and hardware.</li>
    <li>Common applications.</li>
    <li>Web user interface.</li>
    </ul>
    <p>For more information, see <a class="reference internal" href="basic-tasks/projects/index.html"><span class="doc">Working with projects</span></a>.</p>
    </div>
    <div class="section" id="access-control">
    <span id="user-concept-access-control"></span><h2><a class="toc-backref" href="#id3">Access control</a><a class="headerlink" href="#access-control" title="Permalink to this headline">¶</a></h2>
    <p>AEN access controls allow you to:</p>
    <ul class="simple">
    <li>Add and remove project access for new team members.</li>
    <li>Limit the access to specific folders and files to members of
    your project team.</li>
    <li>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.</li>
    </ul>
    <p>Access control is performed from each project&#8217;s Workbench application.</p>
    <p>For more information, see
    <a class="reference internal" href="basic-tasks/projects/control-access-to-project.html"><span class="doc">Controlling access to your project</span></a>.</p>
    </div>
    <div class="section" id="sharing-projects">
    <span id="user-concept-share-project"></span><h2><a class="toc-backref" href="#id4">Sharing projects</a><a class="headerlink" href="#sharing-projects" title="Permalink to this headline">¶</a></h2>
    <p>AEN supports both public and private sharing.</p>
    <p>A project can be &#8220;public,&#8221; which means that anyone with access
    to the system can view the project assets.</p>
    <p>Any content placed in the <code class="docutils literal"><span class="pre">public</span></code> folder in a project is
    publicly accessible using its URL.</p>
    <p>A project can be &#8220;private,&#8221; which means that only the
    project owner and team members can view the project assets.</p>
    <p>You can also <a class="reference internal" href="basic-tasks/projects/control-access-to-project.html"><span class="doc">limit who can access specific files</span></a>.</p>
    <div class="section" id="sharing-jupyter-notebooks">
    <h3>Sharing Jupyter Notebooks<a class="headerlink" href="#sharing-jupyter-notebooks" title="Permalink to this headline">¶</a></h3>
    <p>In addition to general project sharing capabilities, you can also
    publish Jupyter Notebooks to Anaconda Repository. This
    automatically versions the notebook and allows you to define who
    can view the notebook.</p>
    </div>
    </div>
    <div class="section" id="project-tags">
    <h2><a class="toc-backref" href="#id5">Project tags</a><a class="headerlink" href="#project-tags" title="Permalink to this headline">¶</a></h2>
    <p>Tags are used to:</p>
    <ul class="simple">
    <li>Group similar or related projects.</li>
    <li>Identify your project so that it is easier to find.</li>
    <li>Let others know about your project.</li>
    </ul>
    <p>You can <a class="reference internal" href="basic-tasks/projects/tag-project.html"><span class="doc">add and remove tags</span></a> for any project that you have
    access to.</p>
    </div>
