<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>User Management on Documentation</title><link>https://docs.flightpathacademics.com/user-management/</link><description>Recent content in User Management on Documentation</description><generator>Hugo</generator><language>en</language><copyright>FlightPatch Academics</copyright><atom:link href="https://docs.flightpathacademics.com/user-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing Users</title><link>https://docs.flightpathacademics.com/user-management/users/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/user-management/users/</guid><description>&lt;a id="managing-users" name="managing-users"&gt;&lt;/a&gt;



&lt;h1 id="managing-users-header"&gt;Managing Users&lt;a class="anchor" href="#managing-users"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The &lt;strong&gt;Users&lt;/strong&gt; section of FlightPath allows administrators to view and manage user accounts.&lt;/p&gt;
&lt;a id="user-accounts-and-automatic-imports" name="user-accounts-and-automatic-imports"&gt;&lt;/a&gt;

&lt;br&gt;

&lt;h2 id="user-accounts-and-automatic-imports-header"&gt;User accounts and automatic imports&lt;a class="anchor" href="#user-accounts-and-automatic-imports"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Most institutions do not need to create FlightPath users manually. User accounts are typically imported automatically from the institution&amp;rsquo;s &lt;strong&gt;Student Information System (SIS)&lt;/strong&gt; or &lt;strong&gt;Learning Management System (LMS)&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If your institution has an automated user import configured, users should generally be managed in the source system rather than created manually in FlightPath.&lt;/p&gt;</description></item><item><title>Permissions</title><link>https://docs.flightpathacademics.com/user-management/permissions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/user-management/permissions/</guid><description>&lt;a id="permissions" name="permissions"&gt;&lt;/a&gt;



&lt;h1 id="permissions-header"&gt;Permissions&lt;a class="anchor" href="#permissions"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Permissions determine what users can do in FlightPath.&lt;/p&gt;
&lt;p&gt;Permissions are assigned to &lt;strong&gt;roles&lt;/strong&gt;, and roles are assigned to &lt;strong&gt;staff users&lt;/strong&gt;. This allows administrators to manage access without having to configure individual permissions for every user.&lt;/p&gt;
&lt;p&gt;The basic relationship is:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;User → Role → Permissions&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;For example, an advisor might have the &lt;strong&gt;Advisor&lt;/strong&gt; role, and the Advisor role might have permission to search for students, access advising information, and perform advising functions.&lt;/p&gt;</description></item><item><title>Roles</title><link>https://docs.flightpathacademics.com/user-management/roles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/user-management/roles/</guid><description>&lt;a id="roles" name="roles"&gt;&lt;/a&gt;



&lt;h1 id="roles-header"&gt;Roles&lt;a class="anchor" href="#roles"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Roles determine what staff users are allowed to do in FlightPath.&lt;/p&gt;
&lt;p&gt;A role is a collection of permissions. Instead of assigning individual permissions to each user, an administrator creates roles with the appropriate permissions and then assigns those roles to staff users.&lt;/p&gt;
&lt;p&gt;For example, an institution might create roles such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Advisor&lt;/strong&gt; - permissions needed by academic advisors&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Data Coordinator&lt;/strong&gt; - permissions needed by a higher-level user who will be editing degree and course data.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A staff user can have more than one role.&lt;/p&gt;</description></item></channel></rss>