relationship between workspaces and accounts in DevRev
ART-2000_KNOWLEDGE_NODE-25
address.\n\nAccounts are associated with a workspace. An account can be a part of multiple workspaces at the same time. An account can also be linked to multiple opportunities. Accounts help you keep track of your customer contacts. Contacts are always linked to a workspace or an account.\n\nCreate an account\n-----------------\n\nYou can create accounts in the following ways:\n\n### Using the DevRev app\n\n1. Go to **Accounts** > **+ Account**.\n2. Fill in the details like account name,
Accounts | Computer for Growth Teams | DevRev
ART-1414_KNOWLEDGE_NODE-1
__\n\n[Pricing](https://devrev.ai/pricing)\n\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\n\n[API Reference](/public/api-reference/getting-started)[rev-orgs](/public/api-reference/rev-orgs/workspaces)\n\n#\n\nWorkspaces\n\n`rev-orgs` endpoint\n\n\xe2\x84\xb9\xef\xb8\x8f Workspaces (or rev orgs) are the organizations that your customers belong to. A workspace offers more granularity than accounts to define the instances of your product. Users can be mapped
Workspaces — DevRev | Docs
ART-1210_KNOWLEDGE_NODE-0
b'Workspaces | DevRev | Docs\n\n[![]()![]()](https://developer.devrev.ai/)\n\nPublic\n\nPublic\n\nSearch\n\n`/`\n\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\n\nWorkspaces\n==========\n\nCopy page\n\n`rev-orgs` endpoint\n\n\xe2\x84\xb9\xef\xb8\x8f Workspaces (or rev orgs) are the organizations that your customers belong to. A workspace offers more granularity than accounts to define the instances of your product. Users can be mapped to track
Workspaces | DevRev | Docs
ART-1997_KNOWLEDGE_NODE-28
single account. This allows us to consolidate various workspaces under one account.\n\nTo create a new organization in DevRev:\n\n1. Click on your profile picture in the top left corner.\n2. Go to the **Orgs** section and click on **+**.\n3. Fill in the details and click **Create**.\n4. Now you can find your newly created org in **Orgs**.\n\nIn modern SaaS applications, customers often create multiple workspaces for testing, production, and staging. All entities that drive support
Computer for Growth Teams | DevRev
ART-1997_KNOWLEDGE_NODE-27
timeline.\n\nYou can use a customizable set of states and stages to manage the lifecycle of an account, from prospect to customer to churned.\n\n\xf0\x9f\x96\xa5\xef\xb8\x8f Workspace\n------------\n\nA [workspace](https://docs.devrev.ai/product/glossary) represents an instance of a signed-up organization on your application. A workspace is also known as rev-org in the DevRev API. Customers can create multiple workspaces on your application. Therefore, you can link multiple workspaces to a
Computer for Growth Teams | DevRev
ART-1997_KNOWLEDGE_NODE-26
it holds information about the company, including its name, address, industry, domain, and website address.\n\nDevRev leverages convergence to link DevRev accounts with other DevRev entities, including tickets, conversations, opportunities, workspaces, and engagements. This linking offers a 360-degree view of an account across sales, customer success, and support. To enable real-time collaboration among employees from different departments on an account, it provides a discussion
Computer for Growth Teams | DevRev
ART-2933_KNOWLEDGE_NODE-2
[contacts](https://docs.devrev.ai/product/grow#-contact) which represents an individual user associated with the account of the organization. To create a contact, we also need to use the `rev-orgs.list` API with the `accounts` filter to get the default [workspace](https://docs.devrev.ai/product/grow#-workspace)(rev org) created with the account. We will be creating a contact under the workspace (`rev_org`) of the account as contacts (`rev_user`) cannot exist individually without being
Account creation | DevRev | Docs
ART-2002_KNOWLEDGE_NODE-25
about the customer initiating the conversation. Similarly, tickets on DevRev can capture who the ticket was reported by (or reported for).\n\nConcepts\n--------\n\nCustomer identity in DevRev includes the following important constructs:\n\n* **External User/contact**: Your end user or customer or users associated with organization Accounts or Workspaces.\n* **Account/workspace**: Any logical grouping that an external user is part of. It could represent a customer account for your B2B product
Contacts | Computer for Growth Teams | DevRev
ART-15506_KNOWLEDGE_NODE-19
\xe2\x9c\x85 | If neither exists: System creates the account first, then creates the workspace. User is linked to both. If account exists but workspace doesn\xe2\x80\x99t: System creates the workspace under the existing account. User is linked to both. If workspace exists under different account: System returns an error, as workspaces cannot be a part of 2 accounts. |\n| \xe2\x9c\x85 | \xe2\x9d\x8c | If workspace doesn\xe2\x80\x99t exist: System creates a new account and workspace (if needed).
Identify your users with Plug | DevRev | Docs
ART-15506_KNOWLEDGE_NODE-10
preferences, it is not recommended to mark emails as non-unique.\n\n**Attributes for [workspaces](https://developer.devrev.ai/public/api-reference/rev-orgs/workspaces)**\n\n| Attributes | Description | Type | Required | Unique |\n| --- | --- | --- | --- | --- |\n| `workspace_ref` | A unique reference for the user\xe2\x80\x99s workspace. If not provided, and an account reference is passed, the user is directly attached to the account. | string | \xe2\x9d\x8c | \xe2\x9c\x85 |\n| `display_name` |
Identify your users with Plug | DevRev | Docs
ART-16264_KNOWLEDGE_NODE-28
**Account** and **Reported By**. This provides a more streamlined approach to managing customer data.\n* **Automatic workspace display:** When a ticket reporter is associated with a specific workspace within an account, adding that user to the **Reported By** field will automatically reveal three fields: **Account**, **Workspace**, and **Reported By**.\n* **Dynamic user listing:**\n\n  + Upon selection of an account, the **Reported By** list is filtered to show only users associated with that
June 2025 | Changelog | DevRev