User Guide
This guide is for the people who use Nawfe as part of their normal workday.
That usually means office staff, coordinators, approvers, managers, and operations teams who already spend most of their time in business software and need to understand how Nawfe fits into that stack.
What Nawfe is in day-to-day use
At a practical level, Nawfe is where a team goes to run repeatable work in a controlled way.
You use it to:
- start work from a defined process
- complete assigned steps
- route approvals
- review status and history
- work from shared data
Most users do not need to think about platform design first. They need to know where to go, what they are looking at, and what action is expected from them.
The core model
There are three ideas worth getting clear early.
Workspaces hold context
Your workspace determines which processes, data, users, and settings you are working with.
If you belong to more than one workspace, confirm the active one before you work with live data or make changes.
Processes define how work should run
A process is the reusable workflow definition.
It describes the path work follows, what information is collected, and where decisions or approvals happen.
Executions are the live work
An execution is one actual run of a process.
If you are checking status, completing a task, reviewing history, or following up on a specific case, you are usually working with an execution.
Where users spend their time
Home
Use Home as your landing page and quick reference point.
Processes
Use Processes when you need to find a workflow, review the process itself, or start work from a defined process.
Executions
Use Executions when you need to see work that is in flight, review completed work, or open a specific run.
Tables
Use Tables when the work depends on structured records that are shared across workflows or teams.
Settings
Most day-to-day users spend less time here, but managers and workspace admins will use settings for access, structure, connected apps, credentials, and audit review.
Typical working patterns
Most users work in one of these patterns:
Start from a process
Use this when you know which workflow should be used and you need to begin a new piece of work.
Work from the execution list
Use this when you need to monitor in-flight work, clear a queue, review status, or find one specific run.
Open a record first, then follow the process around it
Use this when tables or shared business records are part of how the team works.
Good operating habits
These habits matter more than memorizing screens.
- Keep track of the active workspace.
- Know whether you are looking at a process or an execution.
- Use filters and status views instead of scanning long lists manually.
- Treat shared data as real records, not scratch space.
- Leave work in a state the next person can understand quickly.
When to use which page
| Need | Start here |
|---|---|
| Start a new workflow | Processes |
| Check what is waiting | Executions |
| Review one specific run | Executions |
| Work with shared data | Tables |
| Review the workflow definition | Processes |
| Manage users, permissions, or credentials | Settings |