1.8 Managing Application Express Users

1.8.1 Creating New User Accounts

Workspace administrators can create three different types of user accounts:

• Developers can create and edit applications and view developer activity, session state, workspace activity, application, and schema reports. In Icons view, developers are yellow.

• Workspace administrators perform administrator tasks specific to a workspace, such as managing user accounts, managing groups, altering passwords of users within the same workspace, and managing development services. In Icons view, Workspace administrators are red.

• End users are application users without any access to development or administrative capabilities. In Icons view, end users are green.

To create a new user account:

1. Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

   The Workspace home page appears.

2. Click the Administration icon.

   The Administration page appears.

3. Click Manage Users and Groups.

4. Click Create User.

   The Create User page appears.

5. Under User Identification, enter:

   1. Username - Enter the username used to log 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. Default Schemas - Specify the default schema used for data browsing, application creation, and SQL script execution.

      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.

   2. Accessible Schemas (null for all) - Leave this blank to enable the end user to access all schemas associated with the workspace.

   3. User is a workspace administrator - Select Yes or No to 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.

   4. User is a developer - Select Yes or No to specify if this user should have developer privileges. Developers create and modify applications and database objects and view developer activity, session state, workspace activity, application, and schema reports.

      Developers must have access to either Application Builder, SQL Workshop, or both. Components may not be available if they are switched off by Instance Administrators.

   5. Application Builder Access - Determines whether a developer has access to the Application Builder.

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

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

   8. Set 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 login failures allowed as defined in Workspace Preferences, then the account is locked automatically.

   Tip:

   An Instance administrator can configure these settings for an entire Oracle Application Express instance and define password complexity policies. See "Enabling Login Controls for All Workspaces". "About Strong Password Policies", and "Configuring Password Policies"

7. Under Password:

   • Password - Enter a case-sensitive password.

   • Confirm Password - Enter the password again.

   • Require Change of Password On First Use - Select No to allow the user to use the same password until it expires. Select Yes to require the user to change the password immediately when logging in the first time.

   Tip:

   An Instance administrator can configure these settings for an entire Oracle Application Express instance and define password complexity policies. See "Enabling Login Controls for All Workspaces". "About Strong Password Policies", and "Configuring Password Policies"

8. Under User Groups, optionally select one or more user groups by holding down the CTRL key and selecting the groups.

9. Click Create User or Create and Create Another.

   See Also:

   "Using Groups to Manage Application Express Users" and "Adding and Removing Users from a Group"

1.8.2 Creating Multiple Users Simultaneously

Workspace administrators can create multiple user accounts in a single operation.

To create multiple user accounts simultaneously:

1. Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

   The Workspace home page appears.

2. Click the Administration icon.

   The Administration page appears.

3. Click Manage Users and Groups.

4. On the Tasks list, click Create Multiple Users.

   The Create Multiple Users page appears.

5. In List of Email Addresses, enter or copy and paste email addresses separated by commas, semicolons, or new lines.

6. Under Users:

   • List of Email Addresses - Enter or copy and paste email addresses separated by commas, semicolons, or new lines.

   • Usernames - Specify whether to include or exclude the domain name. Select one of the following:

     • Set username to full email address

     • Exclude @ domain as part of the username

       Removes all text after the @ symbol (for example, user1@xyz.com becomes user1).

7. Under Account Privileges:

   • Default Schemas - Specify the default schema used for data browsing, application creation, and SQL script execution. When using workspaces that have more than one schema available, this schema is the default for creating applications, performing SQL queries, and so on.

   • 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.

   • User is a workspace administrator - Select Yes or No to 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.

   • User is a developer - Select Yes or No to specify if this user should have developer privileges. Developers create and modify applications and database objects and view developer activity, session state, workspace activity, application, and schema reports.

     Developers must have access to either Application Builder, SQL Workshop, or both. Components may not be available if they are switched off by Instance Administrators.

   • Application Builder Access - Determines whether a developer has access to the Application Builder.

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

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

8. Under Password:

   • Password - Specify a password. Passwords are case-sensitive. Developers can change their own passwords. Developers with Administrator privilege can change the passwords of users within the same workspace.

   • Confirm Password - Enter the password again.

9. Click Apply Changes.

1.8.3 Editing Existing User Accounts

Workspace administrators can edit existing user accounts.

To edit an existing user account:

1. Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

   The Workspace home page appears.

2. Click the Administration icon.

   The Administration page appears.

3. Click Manage Users and Groups.

   The Users page appears.

4. You can customize the appearance of the page using the Search bar at the top of the page. See "Customizing Interactive Reports" in Oracle Application Express Application Builder User's Guide.

5. Select a user.

   The Edit User page appears.

6. Under Edit User, update the email address, first name, last name, description, and default date format.

7. Under Account Privileges:

   • Default Schema - Identifies the default schema used for data browsing, application creation, and SQL script execution.

   • Accessible Schemas (null for all) - Enter a colon-delimited list of schemas for which this developer has permissions when using the SQL Workshop. This list of schemas 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.

   • User is a workspace administrator - Select Yes or No to 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.

   • User is a developer - Select Yes or No to specify if this user should have developer privileges. Developers create and modify applications and database objects and view developer activity, session state, workspace activity, application, and schema reports.

     Note that Developers must have access to either Application Builder, SQL Workshop, or both. Components may not be available if they are switched off by Instance Administrators.

   • Application Builder Access - Determines whether a developer has access to the Application Builder.

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

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

   • Account Availability - Select Locked to prevent the account from being used. Select Unlocked to enable the account to be used.

     If the user has exceeded the maximum login failures allowed, specified in Workspace Preferences, then the account is locked automatically.

   Tip:

   An Instance administrator can configure these settings for an entire Oracle Application Express instance. See "Configuring Security Settings".

8. Under Password:

   • Password - Enter a case-sensitive password.

   • Confirm Password - Enter the password again.

   • Require Change of Password On First Use - Select No to allow the user to use the same password until it expires. Select Yes to require the user to change the password immediately when logging in the first time.

9. Under User Groups, optionally select one or more user groups by holding down the CTRL key and selecting the groups.

10. Click Apply Changes.

1.8.4 Deleting or Locking User Accounts

Workspace administrators can delete or lock user accounts.

To delete or lock a user account:

1. Navigate to the Workspace home page.

2. Click the Administration icon.

   The Administration page appears.

3. Click Manage Users and Groups.

   The Users page appears.

4. Select a user.

   The Edit User page appears.

5. To delete a user:

   1. Click the Delete User button.

   2. Confirm your selection and click OK.

6. To lock the account:

   1. Scroll down to the Account Privileges section.

   2. For Account Availability, select Locked.

   3. Click Apply Changes.

1.8.5 Deleting Multiple Users at Once

Workspace administrators can delete multiple user accounts at the same time

To delete multiple user accounts:

1. Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

   The Workspace home page appears.

2. Click the Administration icon.

   The Administration page appears.

3. Click Manage Users and Groups.

4. On the Tasks list, click Delete Multiple Users.

   The Delete Multiple Users page appears.

5. Select the users to be deleted.

6. Click Delete Users.

1.8.6 Changing an End User Password

To change an end user password:

1. Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

   The Workspace home page appears.

2. Click the Administration icon.

   The Administration page appears.

3. Click Manage Users and Groups.

   The Users page appears.

4. Select a user.

   Tip:

   To search for an existing user, enter a query in the Find field and click Go.

5. Under Password, type a new password in the Password and Confirm Password fields.

6. Click Apply Changes.

1.8.7 Viewing the Users Dashboard

The Users Dashboard displays a summary of your account information, users in the current workspace, defined user groups, recently created users, and user status.

To view the Users Dashboard:

1. Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

   The Workspace home page appears.

2. Click the Administration icon.

   The Administration page appears.

3. Click Dashboards.

   The Dashboard page appears.

4. Click Users.

   The Users Dashboard appears listing the following information:

   • Your Account lists information about your account including your username, workspace, account credentials, and email address.

   • Workspace Users lists statistics about all users in the current workspace.

   • User Groups lists all currently defined user groups.

   • Recently Created lists recently created users.

   • User Status lists valid passwords, expired passwords, locked accounts, unlocked accounts, and any accounts for which no email address is defined.

1.8.8 Using Groups to Manage Application Express Users

You can create groups to restrict access to specific features and functions. Note that groups are not portable over different authentication schemes. Groups are primarily useful when used with Application Express Authentication (Internal Cookie User authentication).

Topics:

• Creating a Group

• Editing an Existing User Group

• Adding and Removing Users from a Group