3.12 Managing Users Across an Oracle APEX Instance

An Instance administrator manages all user accounts within an Oracle APEX instance on the Manage Developers and Users page.

• About the Advantages of Managing Users at the Instance Level
  When setting up user accounts, instance administrators can take advantage of security capabilities such as locking accounts, configuring password to have a fixed lifetime, and requiring user passwords be changed on first use.
• About Oracle APEX Accounts Authentication
  User accounts are particularly useful if your application is using Oracle APEX Accounts authentication. APEX Accounts is a built-in authentication method in which user accounts are created and managed in the APEX user repository.
• About Oracle APEX User Roles
  Oracle APEX users are divided into four roles.
• Creating New User Accounts in Administration Services
  Create new user accounts in Administration Services on the Manage Developers and Users page.
• Editing an Existing User Account in Administration Services
  Edit user accounts in Administration Services on the Manage Developers and Users page.
• Deleting User Accounts in Administration Services
  Delete user accounts in Administration Services on the Manage Developers and Users page.

3.12.1 About the Advantages of Managing Users at the Instance Level

When setting up user accounts, instance administrators can take advantage of security capabilities such as locking accounts, configuring password to have a fixed lifetime, and requiring user passwords be changed on first use.

3.12.2 About Oracle APEX Accounts Authentication

User accounts are particularly useful if your application is using Oracle APEX Accounts authentication. APEX Accounts is a built-in authentication method in which user accounts are created and managed in the APEX user repository.

3.12.3 About Oracle APEX User Roles

Oracle APEX users are divided into four roles.

To access the APEX development environment, users sign in to a shared work area called a workspace. Users are divided into four primary roles:

• End users do not have access to development or administrative capabilities. End cannot sign in to a workspace and create applications. End users can only run existing applications.

• Developers are users who create and edit applications, monitor workspace activity, and view dashboards.

• Workspace administrators are users who perform administrator tasks specific to a workspace such as managing user accounts, monitoring workspace activity, and viewing log files.

• Instance administrators are superusers that manage an entire hosted instance using the Oracle APEX Administration Services application. Instance administrators create workspaces, configure features and instance settings, and manage security.

3.12.4 Creating New User Accounts in Administration Services

Create new user accounts in Administration Services on the Manage Developers and Users page.

Tip:

You can also access the Create/Edit User page by clicking Create User on the Workspace Tasks list on the Administration Services home page.

To create a new user account:

1. Sign in to Oracle APEX Administration Services.
2. Click Manage Workspaces.
3. Under Workspace Actions, click Manage Developers and Users.
   The Manage Developers and Users page appears.
4. Click Create User.
   The Create/Edit User page appears.
5. Under User Attributes, enter the appropriate information. Fields marked with an asterisk are required.

   Tip:

   Most attributes in APEX include field-level Help. Attributes with field-level Help, have light gray icon that resembles a question mark (?). To view field-level Help, click the Help icon.

   1. Username - Enter the username used to sign in to the system. Restrictions include:

      • Maximum length of 100 characters

      • No spaces

      • Only these special characters are permitted: ampersand (&) and period (.)

   2. Email Address - Enter the valid email address for this user.
   3. First Name - Enter the first or given name to further identify the user (optional).
   4. Last Name - Enter the last or family name to further identify the user (optional).
   5. Description - Enter comments about this user (optional).
   6. Default Date Format - Specify the default Oracle date format for the user. This option controls the default date format within SQL Workshop.
6. Under Account Privileges:

   1. Workspace - Select a workspace from the list.

   2. Default Schema - Specify the default schema used for this user.

      When using workspaces that have more than one schema available, this schema is the default. This setting does not control security, only the user's preference.

   3. Accessible Schemas (null for all) - Enter a colon-delimited list of schemas for which this developer has permissions when using the SQL Workshop. The list of schemas you enter here restricts the user to a subset of the full set of schemas provisioned for the workspace and determines what schema names the user sees in SQL Workshop.

   4. User is an administrator - Specify if this user should have workspace administrator privileges.

      Administrators are given access to all components. Additionally, they can manage user accounts, groups, and development services. Components may not be available if they are switched off by Instance Administrators.

   5. User is a developer - Specify if this user should have developer privileges.

      Developers must have access to either App Builder, SQL Workshop, or Data Reporter. These components may not be available if they are switched off by the Instance Administrator.

   6. App Builder Access - Determines whether a developer has access to the App Builder.

      An Administrator will always have access to the App Builder.This attribute is always disabled when App Builder Access is disabled for the workspace by an Administrator.

   7. SQL Workshop Access - Determines whether a developer has access to the SQL Workshop.

      An Administrator will always have access to SQL Workshop.This attribute is always disabled when SQL Workshop Access is disabled for the workspace by an Administrator.

   8. Team Development Access - Determines whether a developer has access to the Team Development.

      An Administrator will always have access to Team Development.This attribute is always disabled when Team Development Access is disabled for the workspace by an Administrator.

   9. Data Reporter Builder Access - Determines whether a user has access to Data Reporter.

      An Administrator will always have access to Data Reporter.This attribute is always disabled when Data Reporter Access is disabled for the workspace by an Administrator.

   10. Data Reporter Role - Displays the role for Data Reporter.Instance user management allows defining a data reporter administrator only. Use Data Reporter Manage Users to define other data reporter role for this user.

   11. Account Availability - Select Locked to prevent the account from being used. Select Unlocked to allow the account to be used.

       If the user has exceeded the maximum log in failures allowed, specified in Workspace Preferences, then their account will be locked automatically.

7. Under Password:
   1. Password - Enter a case-sensitive password if you are creating a new account with a password, or are updating the password for an existing account.
   2. Confirm Password - Enter the password again if you are creating a new account with a password, or are updating the password for an existing account.
   3. Require Change of Password On First Use - Select Yes to require the user to change the password immediately after logging in the first time.
8. Click Create User or Create and Create Another.

3.12.5 Editing an Existing User Account in Administration Services

Edit user accounts in Administration Services on the Manage Developers and Users page.

To edit an existing user account in Administration Services:

1. Sign in to Oracle APEX Administration Services.
2. Click Manage Workspaces.
3. Under Workspace Actions, click Manage Developers and Users.
   The Manage Developers and Users page appears.
4. To edit account details, click a user.
5. Edit the appropriate attributes.

   Tip:

   To learn more about an attribute, see field-level Help.

6. Click Apply Changes.

3.12.6 Deleting User Accounts in Administration Services

Delete user accounts in Administration Services on the Manage Developers and Users page.

To delete a user account in Administration Services:

1. Sign in to Administration Services.
2. Click Manage Workspaces.
3. Under Workspace Actions, click Manage Developers and Users.
   The Manage Developers and Users page appears.
4. Click the user to be deleted.
5. Click Delete User.
6. Confirm your selection and click OK.