Oracle APEX Workspace Setup Explained: A Step-by-Step Technical Guide

An Oracle APEX Workspace is the foundation of the Oracle APEX development environment.

Before creating an APEX application, developers typically work within a workspace. The workspace provides an environment where developers can create applications, work with database objects, use SQL Workshop, manage application components, and collaborate with other APEX users.

For developers who are new to Oracle APEX, understanding workspace setup is essential because the workspace connects the APEX development environment with the Oracle Database schema used by applications.

In this article, we will understand:

• What an Oracle APEX workspace is
• APEX Instance vs Workspace
• Workspace and Schema relationship
• Workspace creation
• Schema assignment
• Workspace users
• Workspace login
• Application creation after workspace setup
• Important workspace components
• Common workspace issues
• Best practices

1. What Is an Oracle APEX Workspace?

An Oracle APEX workspace is a shared development environment within an Oracle APEX instance.

It provides developers with access to tools such as:

• App Builder
• SQL Workshop
• Object Browser
• SQL Commands
• Utilities
• Shared Components
• Application development tools
• Workspace administration features

A simplified architecture is:

Oracle APEX Instance
                         |
                         v
                   +-----------+
                   | Workspace |
                   +-----+-----+
                         |
             +-----------+-----------+
             |                       |
             v                       v
       APEX Applications       Workspace Users
             |
             v
       Parsing Schema
             |
             v
      Oracle Database Objects

A workspace is therefore an important boundary for organizing APEX development.

2. APEX Instance vs Workspace

Before setting up a workspace, it is important to understand the difference between an APEX Instance and a Workspace.

APEX Instance

An APEX instance is the overall APEX environment installed and configured for an Oracle Database environment.

Workspace

A workspace is a logical development environment inside that APEX instance.

For example:

Oracle APEX Instance
│
├── HR_WORKSPACE
│
├── FINANCE_WORKSPACE
│
├── SALES_WORKSPACE
│
└── DEVELOPMENT_WORKSPACE

Each workspace can contain its own users and applications.

3. Workspace and Database Schema

One of the most important concepts in APEX is the relationship between a workspace and a database schema.

A workspace can be associated with one or more Oracle Database schemas.

For example:

APEX Workspace
      |
      +-------------------+
      |                   |
      v                   v
  HR_SCHEMA          REPORT_SCHEMA
      |                   |
      v                   v
 HR tables           Reporting views

The schema contains database objects such as:

• Tables
• Views
• Indexes
• Packages
• Procedures
• Functions
• Triggers
• Sequences

The APEX application uses its parsing schema when executing SQL and PL/SQL.

Therefore:

Workspace
    ↓
Application
    ↓
Parsing Schema
    ↓
Database Objects

4. Who Can Create a Workspace?

Workspace creation is an administrative operation.

Depending on the APEX environment and configuration, workspace provisioning may be handled by an APEX instance administrator or through a configured workspace request/provisioning process.

A developer normally does not need to create a workspace every time they create an application.

The typical flow is:

APEX Administrator
       |
       v
Create Workspace
       |
       v
Assign Schema
       |
       v
Create Workspace User
       |
       v
Developer Logs In
       |
       v
Create Application

5. Information Required for Workspace Setup

Before creating a workspace, administrators generally need information such as:

Workspace Name
Workspace Administrator
Administrator Email
Database Schema
Workspace Users

For example:

Workspace Name:
EMPLOYEE_DEV

Schema:
EMPLOYEE_SCHEMA
Administrator:
APEX_ADMIN
Email:
admin@example.com

The exact fields and provisioning workflow can vary depending on whether you are using Oracle APEX in the cloud, Autonomous Database, or a self-managed APEX installation.

6. Creating a Workspace

The exact navigation can vary by APEX version and hosting environment, but the general administrative process is:

APEX Administration Services
          |
          v
Create Workspace
          |
          v
Enter Workspace Details
          |
          v
Select / Create Schema
          |
          v
Create Workspace Administrator
          |
          v
Confirm Workspace

In a self-managed environment, an administrator with the appropriate APEX administration privileges performs workspace provisioning.

7. Step 1 — Open APEX Administration Services

Oracle APEX provides an administration environment separate from the normal developer workspace.

Conceptually:

APEX
│
├── Administration Services
│      └── Manage instance / workspaces
│
└── Workspace
       └── Develop applications

The administrator uses Administration Services to perform tasks such as:

• Workspace management
• User administration
• Instance configuration
• Workspace provisioning
• Monitoring
• Security configuration

8. Step 2 — Create the Workspace

The administrator starts the workspace provisioning process.

A typical workspace creation flow asks for information such as:

Workspace Name
Workspace Administrator
Administrator Email
Schema

For example:

Workspace Name:
EMPLOYEE_DEV

Schema:
EMPLOYEE_SCHEMA

The workspace name should be meaningful and easy for developers to identify.

Examples:

HR_DEV
FINANCE_DEV
SALES_DEV
APEX_TRAINING
EMPLOYEE_PROJECT

9. Step 3 — Assign a Database Schema

The workspace needs access to one or more database schemas.

Suppose the database contains:

EMPLOYEE_SCHEMA

with:

EMPLOYEES
DEPARTMENTS
JOBS
SALARY_HISTORY

The administrator associates that schema with the workspace.

The relationship becomes:

EMPLOYEE_DEV
      |
      v
EMPLOYEE_SCHEMA
      |
      +-- EMPLOYEES
      +-- DEPARTMENTS
      +-- JOBS
      +-- SALARY_HISTORY

This allows APEX applications in the workspace to work with the appropriate database objects, subject to database privileges and APEX configuration.

10. Step 4 — Create the Workspace Administrator

The workspace needs an administrator who can manage the workspace.

The administrator can perform tasks such as:

• Manage workspace users
• Manage applications
• Work with SQL Workshop
• Configure workspace-level settings
• Manage development access

For example:

Workspace:
EMPLOYEE_DEV

Workspace Administrator:
employee_admin

The administrator credentials should be protected and should not be shared among developers.

11. Step 5 — Log In to the Workspace

After the workspace has been provisioned, the developer can access the APEX development environment.

The login process is conceptually:

APEX Login
    |
    +-- Workspace
    +-- Username
    +-- Password

After successful authentication, the developer enters the workspace.

The APEX development environment typically provides access to:

App Builder
SQL Workshop
Team Development
Utilities
Administration

The exact navigation and available features depend on the APEX version and user privileges.

12. Understanding the APEX Home Page

After logging into a workspace, developers typically work with the main APEX development tools.

A simplified view is:

APEX Workspace
│
├── App Builder
│
├── SQL Workshop
│   ├── Object Browser
│   ├── SQL Commands
│   ├── SQL Scripts
│   ├── Utilities
│   └── RESTful Services
│
├── Team Development
│
└── Administration

The availability of specific options depends on the user’s workspace privileges.

13. SQL Workshop

SQL Workshop is one of the most useful tools for an APEX developer.

It provides tools for working with database objects and SQL.

Get Prakash Palani’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Common components include:

Object Browser

Used to inspect database objects.

For example:

EMPLOYEES
DEPARTMENTS
EMPLOYEE_HISTORY

SQL Commands

Used to execute SQL and PL/SQL.

Example:

SELECT employee_id,
       employee_name,
       department_id
FROM employees;

SQL Scripts

Used to create and execute scripts.

Example:

CREATE TABLE departments (
    department_id   NUMBER,
    department_name VARCHAR2(100)
);

14. Create a Test Table

After workspace setup, you can verify that the assigned schema works correctly.

For example:

CREATE TABLE employees (
    employee_id   NUMBER PRIMARY KEY,
    employee_name VARCHAR2(100),
    department_id NUMBER,
    salary        NUMBER
);

Insert sample data:

INSERT INTO employees
    (employee_id, employee_name, department_id, salary)
VALUES
    (1, 'John Smith', 10, 50000);

COMMIT;

Test it:

SELECT *
FROM employees;

If the query works, the workspace/schema configuration is ready for basic development.

15. Create Your First APEX Application

Once the workspace and schema are ready, the next step is to create an application.

The general flow is:

Workspace
   |
   v
App Builder
   |
   v
Create
   |
   v
New Application
   |
   v
Application Name
   |
   v
Pages
   |
   v
Create Application

For example:

Application Name:

Employee Management System

The application can then contain pages such as:

Page 1  - Home
Page 2  - Employee Report
Page 3  - Employee Form
Page 4  - Department Report
Page 5  - Dashboard

16. Workspace → Application → Schema

This relationship is worth remembering.

WORKSPACE
                     |
          +----------+----------+
          |                     |
          v                     v
    Application A         Application B
          |                     |
          +----------+----------+
                     |
                     v
              Parsing Schema
                     |
                     v
              Oracle Database
                     |
        +------------+------------+
        |            |            |
      Tables       Views       PL/SQL

Workspace

Where developers build and manage APEX applications.

Application

The business solution that users interact with.

Schema

The database environment containing the objects and data used by the application.

17. Workspace Users

A workspace can have multiple users.

For example:

EMPLOYEE_DEV
│
├── APEX_ADMIN
├── DEVELOPER1
├── DEVELOPER2
└── TEST_USER

Users can have different responsibilities and privileges.

A typical development environment might have:

Workspace Administrator
        |
        +-- Developer
        |
        +-- Developer
        |
        +-- Tester

User management should follow the principle of granting only the access required for the person’s role.

18. Workspace-Level vs Application-Level Settings

Another important distinction is that not every configuration belongs to the workspace.

Workspace-level examples

Workspace Users
Workspace Settings
Workspace Schema Associations
Workspace Administration

Application-level examples

Pages
Regions
Items
Buttons
Dynamic Actions
Processes
Validations
Authentication
Authorization
Shared Components

Think of it as:

Workspace
   |
   +-- Application 1
   |      ├── Pages
   |      ├── Processes
   |      └── Components
   |
   +-- Application 2
          ├── Pages
          ├── Processes
          └── Components

19. Common Workspace Setup Problems

Problem 1 — Schema Not Available

A developer may not see the expected schema.

Possible causes include:

• Schema is not associated with the workspace
• Workspace configuration is incorrect
• User does not have the required privileges
• Schema/database access is restricted

Problem 2 — Table Does Not Exist

Suppose the application contains:

SELECT *
FROM employees;

but Oracle reports an object-related error.

Check:

1. Which parsing schema is being used?
2. Does the table exist?
3. Does the schema own the table?
4. Are required privileges available?
5. Is a synonym being used?

Problem 3 — Insufficient Privileges

A common issue is:

ORA-00942: table or view does not exist

The object may actually exist, but the parsing schema may not have the required privileges.

For example:

APP_SCHEMA
    |
    | SELECT privilege
    v
HR_SCHEMA.EMPLOYEES

Cross-schema access should be explicitly granted and designed carefully.

20. Workspace Security Best Practices

Workspace setup is also a security concern.

1. Use meaningful workspace names

Avoid unnecessary generic names such as:

TEST
ABC
TEMP

Prefer:

HR_DEV
FINANCE_DEV
CUSTOMER_PORTAL

2. Use individual user accounts

Avoid sharing administrator credentials.

3. Apply least privilege

Give users only the privileges required for their responsibilities.

4. Protect database credentials

Do not publish:

Database passwords
APEX administrator passwords
API credentials
Web credentials

in articles, screenshots, Git repositories, or public posts.

5. Separate environments

Where appropriate, maintain separate environments such as:

Development
     ↓
Testing
     ↓
Production

This reduces the risk of accidental changes to production applications or data.

21. Development vs Production Workspace

For enterprise environments, it is useful to distinguish development and production environments.

For example:

Development
│
└── DEV_WORKSPACE
       |
       └── Development Applications

Testing
│
└── TEST_WORKSPACE
       |
       └── Test Applications

Production
│
└── PROD_WORKSPACE
       |
       └── Production Applications

The exact environment architecture depends on the organization’s deployment strategy.

Applications should be promoted through controlled deployment processes rather than developers directly modifying production without governance.

22. Workspace Setup Checklist

Before starting development, verify:

☐ Workspace created
☐ Workspace administrator created
☐ Database schema associated
☐ Developer users created
☐ Required privileges available
☐ SQL Workshop accessible
☐ Database objects accessible
☐ Application can be created
☐ Application parsing schema verified
☐ Security settings reviewed

This checklist is useful when setting up a new APEX development environment.

23. Complete Workspace Setup Flow

The entire process can be summarized as:

APEX INSTANCE
                   |
                   v
          Create Workspace
                   |
                   v
          Assign Database Schema
                   |
                   v
        Create Workspace Admin
                   |
                   v
          Create Developer Users
                   |
                   v
            Login to APEX
                   |
                   v
             SQL Workshop
                   |
                   v
          Verify DB Objects
                   |
                   v
             App Builder
                   |
                   v
          Create Application
                   |
                   v
          Develop APEX Pages
                   |
                   v
              Test App
                   |
                   v
             Deploy App

24. Workspace Setup — Key Takeaways

The most important concepts are:

Workspace

The APEX development environment.

Schema

The Oracle Database logical container that owns database objects.

Application

The APEX application built inside the workspace.

Parsing Schema

The database schema used for executing an application’s SQL and PL/SQL at runtime.

The overall relationship is:

APEX Instance
      |
      v
Workspace
      |
      v
Application
      |
      v
Parsing Schema
      |
      v
Database Objects

Once this relationship is understood, many APEX concepts become much easier to understand.

Conclusion

Setting up an Oracle APEX workspace is the first major step in creating a structured APEX development environment.

A correctly configured workspace provides developers with access to the APEX development tools while connecting applications to the appropriate Oracle Database schemas.

The key architecture to remember is:

APEX Instance → Workspace → Application → Parsing Schema → Database Objects

Understanding this relationship is especially important when working with SQL Workshop, application development, database privileges, parsing schemas, security, deployment, and troubleshooting.

For an Oracle APEX developer, workspace setup is not simply an administrative task. It establishes the foundation on which the application’s development, database access, security, and deployment processes operate.

Official Oracle Documentation

For the exact workspace-provisioning steps, always refer to the documentation for the APEX version and hosting environment you are using, because the UI and provisioning options can differ between APEX Cloud/Autonomous Database and self-managed installations.