Developers Overview
This section is for people building apps for Nawfe, not for day-to-day workspace users.
Use it when you need to:
- open the developer portal
- create and manage an app
- work with draft and published app versions
- generate install links
- manage secrets, members, and webhook behavior
What the developer portal is
The developer portal is a separate Nawfe surface focused on apps.
It is where you manage:
- the app record itself
- app versions
- install and distribution rules
- secrets
- app team access
- webhook analytics
If the main Nawfe app is where teams run work, the developer portal is where app builders shape how their app enters that world.
What you need before you start
In practice, most developers need three things in place:
- access to the developer portal
- acceptance of the current developer terms
- the right permission level to create, edit, publish, or manage apps
If those are not in place, the portal will feel locked down because it is.
The main app model
There are a few ideas worth getting straight early.
An app has a stable identity
The app record holds things like name, slug, client ID, service user, and general distribution state.
That identity stays stable while versions change over time.
Versions carry the working behavior
Draft versions are where you edit and validate the manifest.
Published versions are what normal installs follow.
Installs connect an app to a workspace
An install is where a workspace actually starts using the app.
Published installs follow the live published channel. Draft installs can be pinned to a specific draft version for preview work.
The main areas you will use
Dashboardfor app list, quick stats, and app creationGeneralfor app identity, distribution, and install allowlistsVersionsfor draft work, publish flow, and install linksSecurityfor members, client secrets, and webhook secretsWebhooksfor aggregate delivery analytics across installed workspaces