Developer apps belong to a Realsee Passport Team. A Team can be an individual, a company, or another organization, so the dashboard uses Team language instead of company-only wording.
Team scope
The active Passport Team controls what the dashboard shows:
- App request history for that Team.
- Provisioned Developer apps for that Team.
- Credential actions available to owners of that Team.
Switch Teams before submitting a request if the integration should belong somewhere else.
Submit
Use Submit App request when a Team needs a new Developer app. The active Team is the authoritative owner; the form captures the app name, contact details, and production use case without accepting a second editable Team name. The portal records the request and shows it in history immediately.
Review
Realsee reviews the submitted Team and use case before provisioning credentials. The review step prevents credentials from being issued to the wrong Team and gives Realsee enough context to enable the right capabilities.
If more context is needed, someone from Realsee may contact the email submitted on the request.
Credentials
After provisioning, the Developer app appears in the Team's app list. Use the dashboard to inspect its app key (AK), XID, and credential actions. Keep server-side secrets out of browser code and logs.
The app request remains useful after provisioning because it records who requested the app, which Team owns it, and what use case was reviewed.
Duplicates
The dashboard compares normalized app names within the same Team. A same-name App request that is still unprovisioned and less than 30 days old blocks a duplicate submission. A provisioned Developer app with the same name does not block a new request.