> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/architecture/rox-architecture.md). # Platform Architecture Rox connects enterprise data and public information to give its revenue agent the context it needs to research accounts, prepare for meetings, support outreach, and work with opportunities. The platform brings together three parts: a System of Context that organizes revenue information, an agent that retrieves context and uses tools, and applications where users review information and work with the results.
### System of Context Revenue information is distributed across CRM records, emails, meetings, documents, and public sources. The System of Context connects this information around accounts, people, opportunities, and interactions. Entity resolution identifies records that refer to the same company or person. Relationships connect those records to the activities and opportunities they belong to. Source mappings preserve the connection between Rox entities and the systems the data came from. This gives the agent a connected view of an account rather than a collection of unrelated records. For example, meeting context can combine an opportunity’s CRM details with related conversations and account research. The data available in Rox depends on the organization’s connected sources and configuration. See [**System of Context**](https://www.rox.com/docs?page=architecture/system-of-context) for more on how that information is organized. ### The revenue agent Users work with Rox through a revenue agent that can retrieve information and use tools across different tasks. For a given request, Rox retrieves relevant context using information such as the account, participants, time period, and task. Retrieval can include relevance scoring to select useful information before it reaches the agent. The agent uses that context to produce an answer or work with supported tools. Depending on the task, the result might be an account summary, an editable email draft, a list of contacts, or an update to a record. Structured outputs allow results to appear as usable objects in the application. An email draft can be reviewed and edited; contact results can be used in a subsequent workflow. The actions available depend on the feature, connected integrations, and the user’s permissions. ### Applications and workflows The web application brings together account and people views, research, sequences, opportunities, and agent conversations. Rox for Mac supports meeting workflows alongside the web experience. These interfaces give users ways to supply instructions, inspect supporting information, and work with agent outputs. Integrations connect supported workflows to external systems, including CRM and communication tools. For feature instructions, see the [**User Guide**](https://www.rox.com/docs?page=user-guide/rox-for-mac). For connection requirements and setup, see [**Admin Guide → Integrations**](https://www.rox.com/docs?page=admin-guide/integrations). ### Governance and access Governance determines what users can access and change in Rox. Resource permissions, record access, and field permissions work together: access to a record does not automatically grant permission to edit it or view every field. These controls provide the access model for working with connected revenue data. Administrators configure defaults, Pods, hierarchies, and Permission Sets, and use Access Provenance to inspect how access is granted. Connecting a data source, assigning an account, and granting access serve different purposes. Administrators should configure and verify each as part of deployment. See [**Admin Guide → Governance**](https://www.rox.com/docs?page=admin-guide/governance) for the access model and configuration instructions, and [**Security**](https://www.rox.com/docs?page=security/secure-by-design) for information about data protection. ### Data access and freshness Rox can work with structured enterprise data through native warehouse sharing or replication into a Rox-managed environment. The appropriate approach depends on the source and deployment configuration. Source availability and downstream processing both affect when a change becomes usable in Rox. A change available in a source system is not necessarily reflected immediately in every view or agent response. See [**Warehouse Data Access**](https://www.rox.com/docs?page=architecture/warehouse-data-access) for the differences between sharing and replication.