3. Roles you need for this guide

Permissions in OpenApp are roles attached to your user inside each org (not globally on your account).

Your personal workspace gives you the admin role, which is enough to manage integrations, devices, entities, and API keys for the rest of this guide.

If you ever work in someone else’s org instead, you need equivalent roles there; see Roles and ask that org’s administrator. For the full model, see Organizations, Users, and Roles; the API reference matches the same rules.

Why learn organizations, users, and roles?

OpenApp is a security product: the core job is to let you decide which entity—a person, a group, or another actor—may access which resources, and to enforce that consistently. Organizations, users, and roles are the building blocks for that. They give you enough structure to stay flexible as your setup grows, stay ergonomic in the dashboard and API, and stay expressive enough that your access rules read clearly: you can form a solid mental model of who can do what, explain it to others, and maintain it as people and systems change. That vocabulary is there to help you reach your goals safely—it is not there to slow you down.

In this org your admin role is enough for every dashboard step that follows. Browsers use your normal login; programs need a separate credential—the next step creates an API key you will reuse for HTTP and SDK examples.

---

← Personal workspace · Create an API key →