Users

What a planner means

Users is the login-account dialog. Oracle Admin Menu: "Opens the Users dialog box. Use the Users dialog box to add and remove users, and assign global and project profiles to users." Enabled when "All." Corresponding toolbar: Administrator Toolbar. How-to pages: Admin, Users.

Oracle Users (P6 Professional Only): "A user account provides a secure means for a person in your organization to access and use P6 Professional, however a user account alone isn't sufficient to access the software. A user account requires access to modules, and to be assigned security profiles. You might also need to assign your user access to resources."

Oracle Users dialog box: "If your security privileges enable you to edit users, use this dialog box to add and remove users, assign global and project profiles to users, and enable or disable access to projects and listed modules."

This dialog is accounts and assignment. It is not Admin > Security Profiles (privilege-set definitions). See Security Profiles. It is not Edit > User Preferences (per-user display and session). See User Preferences. It is not Admin Preferences (enterprise defaults, including Password Policy). See Admin Preferences. It is not OBS (Responsible Manager tree). See OBS. It is not Activity Owners (TASKUSER). See Primary Resource. It is not EPPM User Administration pages (a different admin surface; see below).

Professional dialog tabs Oracle names

Oracle Users dialog box lists these tabs (quote Oracle's printed names):

• General tab
• Contact tab
• Global Access tab
• Project Access tab
• Module Access tab

Buttons / chrome Oracle named on that page (not a field catalog): Display Options bar; Users table ("Lists login names and additional information for users."); Add; Delete; Count.

Add — Native: "the Add User dialog box will appear." LDAP: "a dialog box appears that you use to search for and import users into P6 Professional from your LDAP repository." "If resource security is enabled, the new user automatically gets no access to resources. Click the Global Access tab to change the user's resource access settings."

Count — "Displays the Count dialog box, which lists the number of users assigned access to each listed module. It also provides the user name of each user assigned access to each module." How-to List number of users: Admin, Users → Count. "Expand a module to display the user name of each user assigned access to a module." Print prints "the same as it appears on the screen."

Oracle Note on the dialog: "If you have restricted (or no resources access), the dialog filters out" users that have all resource access, and users that have restricted access with a root resource outside your resource access. "If you have all resource access or you are an Admin Superuser, you can view all users." "For the Module Access tab, you must mark the applicable checkboxes for all users, including Admin Superusers."

Do not invent a Users-table column list. Quote the tab pages.

General — Oracle General tab fields:

• Login Name — "The selected user's login name. You can type a new login name, between 1 and 255 characters." LDAP: "the login name you enter is checked against the LDAP store. If the user is not found, a message displays to notify you that the user cannot be added."
• Personal Name — "The selected user's name. You can type a new name."
• Password — "Click to change the selected user's password. To change your own password, select your user name, then click this button." Length: "A password must be between 1 and 20 characters." If Admin Preferences Enable password policy is selected: "a minimum of 8 characters long, and that contains one alpha and one numeric character." If not selected: "up to 20 characters long." LDAP: "the Password button does not appear since password management is handled through the directory server." How-to Change user passwords: "Passwords are case-sensitive." "Passwords that were set before the new password policy was enabled are valid and usable." Password Policy lives on Admin Preferences, not this dialog. See Admin Preferences. The User Preferences Password tab is the signed-in user changing their own password. See User Preferences.
• Resource ID / Resource Name for Personal Calendar — "The selected user's resource name. Click to select a resource." Add new users: "If the ability to edit a personal resource calendar is required, you can select an associated resource from the Resource ID / Resource Name for Personal Calendar field, or you can create the link when you add resources."

Oracle Users (overview) username/password rules (quote; do not invent a longer catalog): "Login names for users must be between 1 and 255 characters long." Enable Password Policy cleared: "passwords must be between 1 and 20 characters long." Selected: "passwords must be at least 8 characters long and must contains at least one alpha and one numeric character." (Oracle's "contains" as printed.) "Oracle recommends the use of strong passwords. Strong passwords in P6 Professional are defined as passwords containing between 8 to 20 characters and at least one numeric and one alpha character."

Contact — Oracle Contact tab fields: email Address; Office Phone. "If a user is also a resource, the email address and office phone number you type in the Users dialog box overwrites the email address and office phone number recorded in the Resources window General tab, if that information is different. Likewise, email and phone information you enter in the Resources window overwrites the information in the Users dialog box."

Global Access — Oracle Global Access tab fields:

• Global Security Profile — "The selected user's security profile. Each security profile has specific access privileges associated with it. You can select another security profile." How-to Assign global profiles: Admin, Users → Global Access tab → "select a global security profile." The privilege set is Admin > Security Profiles. See Security Profiles.
• Resource Access — "The selected user's resource access." Oracle names three grants: All Resource Access ("access to all resources with no restriction. This option disables resource security."); No Resources (All Resource Access cleared and Resource Access empty — "the default access for new users"); Resource Nodes ( Root Nodes) (All Resource Access cleared and one or more resources — "the assigned resource nodes and all their children"; "A user can be assigned to up to five root resource nodes."). "Resource security settings are honored the next time the user logs in."

Oracle Users (overview): "By default, new users do not have access to resources." Setting up user security: "Admin Superusers automatically get All Resource Access." Add new users: "When you create new users, they are automatically assigned the default global profile."

Project Access — Oracle Project Access tab fields:

• Responsible Manager — "Lists the organizational breakdown structure (OBS) element whose project information the selected user can access. A user can only access project information that relates to the specified responsible manager."
• Security Profile — "Lists the selected user's project profile, or access privileges, for projects assigned to the corresponding responsible manager." Double-click to change.
• Assign / Remove — assign or remove "the selected user's access to an OBS element's project information."

How-to Assign project profiles: Admin, Users → Project Access tab → Assign → OBS element/responsible manager → Security Profile field. Setting up user security: "This grants the user access to WBS elements (and associated activities) for which the assigned OBS element is responsible, in all projects." "A user is not required to have a profile for every OBS element. However, unless a user's global profile is Admin Superuser, a user cannot access project information without a project profile." OBS access is not inherited down child OBS elements. See OBS.

Module Access — Oracle Module Access tab: Product ("Lists the product that can be enabled or disabled for each user."); Access ("A marked checkbox indicates that the selected user can access the corresponding application."). Products Oracle named on that tab: Visualizer ("Provides access to Visualizer."); Project Management ("Provides access to P6 Professional."). "You must mark the applicable checkboxes for all users, including Admin Superusers."

Oracle Users (overview) module list: "The modules available for P6 Professional are: P6 Professional; P6 Visualizer. You can assign a user access to either or both." Oracle Module access: "The P6 Professional module access option controls whether users can attempt to log into the P6 Professional application." "The Visualizer module access option controls whether users can attempt to log into the Visualizer application." Quote both the tab labels (Project Management / Visualizer) and the overview names (P6 Professional / P6 Visualizer). Do not collapse them. How-to Enable or disable: Admin, Users → Module Access tab → Access column.

Oracle Users (overview) setup order: "Add a new user." "Assign the user access to the modules they will need to use." "Assign a global security profile." "Assign project security profiles to OBS nodes." "Users you create will not have access to any projects or features until you assign them a security profile."

Admin Superuser / Project Superuser assignment — this dialog assigns those profiles. Who may apply them: Oracle's pages disagree; quote both. Do not pick a winner.

• Setting up user security: "Only an Admin Superuser can add, edit, or delete Admin Superusers or change an Admin Superuser's password." "Only an Admin Superuser can apply the Admin Superuser profile to a user. Any user with the Add/Edit/Delete Users privilege can apply the Project Superuser profile to a user."
• Assign global profiles: "You can apply the Admin Superuser profile to as many users as you like." "Only an Admin Superuser can apply the Admin Superuser profile to a user."
• Assign project profiles: "Only an Admin Superuser can apply the Project Superuser profile to a user."

Remove — Oracle Remove users: Admin, Users → select user → Delete → Yes.

Offline note Oracle printed on Setting up user security / Change user security profiles: avoid changing "User details, Global or project security profiles, OBS assignments (both for users and for projects), and Resource security" while a user is working offline. Check Out: security profile does not apply; all project data is exported. See Check Out.

Professional pages fetched do not print EPPM Deactivate User, Copy user, User Interface View, Contributor, or the EPPM module-access list (Projects / Portfolios / Resources / Team Member / …). Do not copy those onto this dialog.

EPPM — User Administration / Users, not Admin > Users

Oracle About User Access: Users — "Enables you to modify security attributes and project and module access for all users of P6 EPPM modules." Getting Here on the Module Access detail window: Administration → User Administration → Users.

Oracle About Users: "The term user is a shortened form of the full reference to a user access account." "The Users page allows you to add and remove users, assign global and project profiles to users, set resource access, and assign or remove access to projects and P6 EPPM modules." Example Oracle printed: "you can assign a user an Admin Superuser security profile … or you can assign a user no global privileges." "you can use the project access tab to assign responsible managers and give them project-level security profiles, such as Contributor."

Oracle Module Access Detail Window of the Users Page: "Users cannot log into P6 without one of the following module access options selected: Projects, Portfolios, Resources, Contributor, or Enterprise Reporting." If the user "only has a P6 Professional, Analytics, Team Member Interfaces, P6 Integration API, or P6 EPPM Web Services license, they will be prompted that they don't have a valid license." Modules Oracle named on that page (quote; do not copy onto Professional): Contributor; Enterprise Reports; Integration API; P6 Analytics; P6 Professional; Portfolios; Projects; Resources; Team Member; Timesheet; Visualizer; Web Services.

EPPM surfaces Oracle named that Professional Users pages fetched do not print: Deactivate User (Deactivating User Accounts: "Deactivate the account instead of deleting the user if the user uses P6 Team Member or when you need to retain the history of actual working hours"); Copy / paste a user (About Users lists what is copied vs not); User Interface View; Associated Resource. Do not invent them on Admin > Users.

Do not copy Professional Admin > Users, Administrator Toolbar, Count, Native Add User dialog, Project Management / five-tab list, or the Professional Superuser-assignment conflict onto EPPM User Administration. Do not copy EPPM Deactivate User, Copy, User Interface Views, Contributor, or the EPPM module list onto this Professional dialog. Professional Users pages fetched do not say "when connected to a P6 EPPM database, do those tasks using P6." Do not invent that redirect (Security Profiles create/assign pages do print it for profiles; that is not this dialog).

XER

Users is an enterprise / database dialog. It is not an XER table.

Oracle's project XER data map TOC lists no USERS, USER, USERENG, USEROBS, or USERPROF table. Do not invent a USERS / USER %T or columns for Login Name, Personal Name, Password, Contact, Global Security Profile, Resource Access, Project Access OBS/profile rows, or Module Access checkboxes.

TASKUSER is Activity Owners (user_id labeled Owner). It is not a user account and not this dialog. See Primary Resource.

OBS is the OBS tree (Responsible Manager). User-to-OBS / project-profile assignments are not on the cited project map. See OBS.

RSRC.user_id is labeled User Login Name. That is a resource-to-user pointer on the resource, not a Users table. RSRC.ts_approve_user_id is Timesheet Approval Manager. See Timesheets Are Approved Hours; Apply Actuals Posts Them and RSRC / TASKRSRC (and Roles / Prices).

PROJECT.checkout_user_id is Checked Out By. That is a checkout pointer, not this dialog. See Check Out.

A Viewer parse of one project XER cannot reconstruct Users (login accounts, passwords, Global Access, Project Access, Module Access, resource-security roots, or Count). Oracle Importing Projects using Primavera XER Format: "The Activity Owner field shows the P6 EPPM user who owns the activity. If a Primavera XER file that includes the Activity Owner field is imported into a database, the Activity Owner data is imported only if the user already exists in the database." That is TASKUSER join-to-existing-user, not a Users export.

Microsoft Project

Desktop Project has no Users dialog and no Global Access / Project Access / Module Access admin surface.

Microsoft Windows User Account (resource field) is a Resource Sheet text field: "the Microsoft Windows user name you enter for a work resource." "This field is used to identify and verify authorized Windows users when they are logging on to Project Server." "The Windows User Account field is not available for material resources." That is a resource field for Project Server login, not P6 Admin > Users.

Microsoft Add user accounts in Project Server is Project Web App: Server Settings → Security → Manage Users → New User. Identification, User Authentication, Assignment Attributes, Security Groups, Security Categories, Global Permissions. "Every Project Web App user must have a user account before he or she can log on to Project Web App." That is Project Server / PWA, not desktop Project.

Microsoft Plan user access in Project Server is SharePoint permission mode vs Project permission mode. That is PWA security modes, not P6 Users.

They are not the same object. Do not map P6 Users to a Resource Sheet Windows User Account, to File > Options, to SharePoint groups, or to Project Server Manage Users as the same dialog. Do not claim MPXJ can write a real MPP.

Don't

• Treat Users as Security Profiles, as User Preferences, as Admin Preferences, as OBS, as TASKUSER Activity Owners, as EPPM User Administration, or as project XER data.
• Invent a USERS / USER / USERENG / USEROBS / USERPROF XER table, or treat TASKUSER, OBS, or RSRC.user_id as "the Users dialog."
• Claim a Viewer reconstructed Users (accounts, access tabs, or Count) from a project XER.
• Invent a user-field catalog Oracle did not print, or collapse Project Management (Module Access tab) and P6 Professional (overview / Module access page), or Visualizer and P6 Visualizer.
• Copy Users All Resource Access / Module Access onto Security Profiles, or treat profile definition (Admin > Security Profiles) as this assignment dialog.
• Copy Professional Admin > Users / five-tab list / Count / Administrator Toolbar onto EPPM User Administration, or copy EPPM Deactivate / Copy / User Interface Views / Contributor / the EPPM module list onto this Professional dialog.
• Invent an EPPM-database "do Users in P6" redirect that Professional Users pages fetched do not print.
• Pick a winner among the Superuser-assignment sentences.
• Map P6 Users to MSP Windows User Account or Project Server / PWA Manage Users as the same object.
• Claim MPXJ writes a real MPP.