Accounts, Applications & Workspaces Explained

Understanding the core structure of how Rayven is organised

Overview

In Rayven, everything you build is part of a structured hierarchy that starts with your Rayven Account, under which you create Applications, each managed through the Workspace. This page explains how these elements relate to each other and how they are used when building or managing your solutions in Rayven.

Rayven Account, Applications and Workspace

Rayven Account

A Rayven Account belongs to you, your business or organisation. It acts as a container for all your applications and workspace users. A single Rayven Account can contain multiple Applications, each with its own data, workflows, interfaces, and users.

• Think of the account as the top-level access point for your organisation.

• Each person with backend access is a Workspace User under your account. 

• Your Rayven Account can have multiple Workspace Users

• All applications in your account are isolated: they don’t share data or configurations unless explicitly set up to do so.

Applications

An Application in Rayven is a fully standalone software solution that includes its own:

• Tables (structured data)

• Workflows (data processing and logic)

• Interfaces (frontend pages for end users)

• Users (App Interface users)

You might build one application for customer onboarding and another for asset management—each one will be isolated and can have its own permissions, data models, UI, and Users.

Each application is typically built and configured by Workspace Users and accessed by Application Users (also referred to simply as "Users").

The Workspace

The Workspace is the development environment where applications are built and maintained. It is only accessible to Workspace Users. 

From the workspace, you can:

• Create new applications

• Configure application elements (tables, workflows, interfaces, and users)

• Manage workspace-level settings such as user access, roles, and branding

Access the Workspace here: https://workspace.rayven.io

Key Relationships and Responsibilities

Common Use Cases for Each

• Account: Your organisation’s access to Rayven as a platform.

• Application: A software product or business tool, such as a CRM, dashboard, or workflow engine.

• Workspace: Where technical users set up tables, logic, data flows, and frontend interfaces.

Example Structure

Here’s an example of how it might be structured:

• Account: "Acme Corp"

  • Application 1: "Customer Feedback Tool"

  • Application 2: "Supplier Tracker"

  • Application 3: "Energy Monitoring Dashboard"

• Each application has its own set of:

  • Tables (structured data)

  • Workflows (automation & logic)

  • Interfaces (what users see)

  • Users (with custom permissions)

Summary

Rayven’s architecture separates your organisation’s access (the Account) from each solution you build (Applications), which are managed by Workspace Users through the Workspace. Understanding this structure is essential for managing access, building modular solutions, and scaling across use cases within a single environment.

FAQs

What’s the difference between a Rayven Account and an Application?
A Rayven Account is the top-level container owned by your organisation. An Application is a standalone product built within your Account.

Can I have multiple Applications in one Account?
Yes. You can build and manage as many applications as needed under a single Rayven Account.

Can data be shared between Applications?
Not by default. Applications are siloed, but data can be shared if configured explicitly using workflows and APIs.

Who can access the Workspace?
Only Workspace Users have access to the Workspace. Application Users can only access the front-end interfaces of specific applications.

Do Workspace Users automatically have access to all applications?
Only SuperAdmin users do. Other Workspace Users must be granted access to individual applications via the Access Roles menu.

What URL do Application Users use to access their app?
Application users access their interfaces via https://app.rayven.io or via a whitelabelled URL if configured.