Skip to main content

Workspaces

A workspace is the main container for your work in Nawfe.

It holds the things that belong together:

  • processes
  • executions
  • tables
  • users
  • teams
  • credentials
  • connected apps
  • settings

Why workspaces exist​

Not every process belongs in the same place.

Teams use separate workspaces to keep work organized, reduce mistakes, and control who has access to what.

You can have more than one workspace​

One account can belong to multiple workspaces.

That is useful when you need to separate work by purpose, such as:

  • different projects
  • private use
  • different teams or clients
  • a development environment for process testing

Using a dev workspace is often the right move when you want to build and test process changes before turning them into something reusable in the template store.

Switching between workspaces​

Switching between workspaces should feel routine.

You do not need separate accounts just because your work is split across different environments or projects.

The important thing is to stay aware of which workspace is active before you:

  • edit a process
  • publish changes
  • create data
  • invite users
  • configure credentials

A simple way to think about it​

Use workspaces to separate work that should not be mixed.

If the users, data, process versions, or settings need different boundaries, they probably belong in different workspaces.

Common workspace patterns​

Personal or private​

Use a private workspace when you want a clean place to experiment or manage your own processes.

Development and testing​

Use a dev workspace when you want to build or test process changes before sharing them more widely.

That helps avoid accidental changes in the wrong environment.

A practical habit​

A good habit is to check the active workspace before making changes or reviewing data.

That keeps the rest of your work grounded in the right environment.