Database Reference
In-Depth Information
locks and settings, and so on. Although it isn't good practice, the Work-
space Administrator can also act as a Developer, creating and modifying
applications.
Developers
are the users who create and edit the applications in the
workspace. They have access to the underlying tables in the schema(s)
assigned to the workspace and may create and modify database objects
and stored PL/SQL units. Most people writing APEX applications only
need this level of access.
End Users
are only able to run applications in a workspace. They don't
have direct access to any of the underlying database objects, nor do they
have access to any of the APEX development modules. End users can't
log directly into a workspace.
With the exception of the APEX Instance Administrator, APEX users are specific
and unique to a workspace, meaning you can have a user with the same name in mul-
tiple workspaces in a single APEX instance but each of these users is unique. They can
have their own passwords and settings and aren't linked together in any way.
When you're developing, you should get in the habit of logging in as a Developer as
opposed to a Workspace Administrator. Several safeguards are available to help keep
developers from stepping on each other in a workspace. If you log in as a Workspace
Administrator, these safeguards are bypassed, and you may accidently interfere with
something someone else is working on. Although this isn't a problem in a workspace
with only one developer, it's still good to get into that habit.
Note
This topic uses the last three types of user. It assumes that APEX has been in-
stalled, a workspace has been created, and you have been given the Workspace Admin-
then the username you were given when you signed up has the credentials of a Work-
space Administrator. If, however, you're using a local instance, either refer to the APEX
documentation or get your Instance Administrator to help you set up a workspace.
Applications, Pages, Regions, and Items
Although a workspace starts off basically empty, you can have many applications that
reside in a workspace. There is no specific rule, but it's likely that all the applications
in a workspace share something: they might all use the same underlying database ob-
