--- title: "Projects" description: "A non-technical ecosystem overview of Projects in RevCent, focused on how Projects act as durable context workspaces that organize related RevCent features, preserve decisions, connect Project Notes, and help AI, MCP, users, and external agents understand ongoing work across the RevCent ecosystem." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/Project.md" relationships: - name: "Project Note" url: "https://revcent.com/documentation/markdown/ecosystem/item/ProjectNote.md" technical_links: api: section: "https://revcent.com/docs/api/v2#section-projects" operations: - name: "Get Projects" operation_id: "GetProjects" operation: "https://revcent.com/docs/api/v2#operation-GetProjects" schema: "https://revcent.com/documentation/files/api/operation/GetProjects.json" - name: "Create A Project" operation_id: "CreateProject" operation: "https://revcent.com/docs/api/v2#operation-CreateProject" schema: "https://revcent.com/documentation/files/api/operation/CreateProject.json" - name: "Get A Project" operation_id: "GetProject" operation: "https://revcent.com/docs/api/v2#operation-GetProject" schema: "https://revcent.com/documentation/files/api/operation/GetProject.json" - name: "Edit A Project" operation_id: "EditProject" operation: "https://revcent.com/docs/api/v2#operation-EditProject" schema: "https://revcent.com/documentation/files/api/operation/EditProject.json" - name: "Delete A Project" operation_id: "DeleteProject" operation: "https://revcent.com/docs/api/v2#operation-DeleteProject" schema: "https://revcent.com/documentation/files/api/operation/DeleteProject.json" - name: "Associate Entity with Project" operation_id: "ProjectAssociateEntity" operation: "https://revcent.com/docs/api/v2#operation-ProjectAssociateEntity" schema: "https://revcent.com/documentation/files/api/operation/ProjectAssociateEntity.json" - name: "Disassociate Entity with Project" operation_id: "ProjectDisassociateEntity" operation: "https://revcent.com/docs/api/v2#operation-ProjectDisassociateEntity" schema: "https://revcent.com/documentation/files/api/operation/ProjectDisassociateEntity.json" - name: "Search Projects" operation_id: "SearchProjects" operation: "https://revcent.com/docs/api/v2#operation-SearchProjects" schema: "https://revcent.com/documentation/files/api/operation/SearchProjects.json" - name: "Get Project Notes" operation_id: "GetProjectNotes" operation: "https://revcent.com/docs/api/v2#operation-GetProjectNotes" schema: "https://revcent.com/documentation/files/api/operation/GetProjectNotes.json" - name: "Create A Project Note" operation_id: "CreateProjectNote" operation: "https://revcent.com/docs/api/v2#operation-CreateProjectNote" schema: "https://revcent.com/documentation/files/api/operation/CreateProjectNote.json" - name: "Get A Project Note" operation_id: "GetProjectNote" operation: "https://revcent.com/docs/api/v2#operation-GetProjectNote" schema: "https://revcent.com/documentation/files/api/operation/GetProjectNote.json" - name: "Edit A Project Note" operation_id: "EditProjectNote" operation: "https://revcent.com/docs/api/v2#operation-EditProjectNote" schema: "https://revcent.com/documentation/files/api/operation/EditProjectNote.json" - name: "Delete A Project Note" operation_id: "DeleteProjectNote" operation: "https://revcent.com/docs/api/v2#operation-DeleteProjectNote" schema: "https://revcent.com/documentation/files/api/operation/DeleteProjectNote.json" - name: "Search Project Notes" operation_id: "SearchProjectNotes" operation: "https://revcent.com/docs/api/v2#operation-SearchProjectNotes" schema: "https://revcent.com/documentation/files/api/operation/SearchProjectNotes.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md" operations: - name: "Get Projects" operation_id: "GetProjects" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetProjects.md" available_via_ai: true - name: "Create A Project" operation_id: "CreateProject" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateProject.md" available_via_ai: true - name: "Get A Project" operation_id: "GetProject" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetProject.md" available_via_ai: true - name: "Edit A Project" operation_id: "EditProject" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditProject.md" available_via_ai: true - name: "Delete A Project" operation_id: "DeleteProject" markdown: "https://revcent.com/documentation/markdown/mcp/operation/DeleteProject.md" available_via_ai: true - name: "Associate Entity with Project" operation_id: "ProjectAssociateEntity" markdown: "https://revcent.com/documentation/markdown/mcp/operation/ProjectAssociateEntity.md" available_via_ai: true - name: "Disassociate Entity with Project" operation_id: "ProjectDisassociateEntity" markdown: "https://revcent.com/documentation/markdown/mcp/operation/ProjectDisassociateEntity.md" available_via_ai: true - name: "Search Projects" operation_id: "SearchProjects" markdown: "https://revcent.com/documentation/markdown/mcp/operation/SearchProjects.md" available_via_ai: true - name: "Get Project Notes" operation_id: "GetProjectNotes" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetProjectNotes.md" available_via_ai: true - name: "Create A Project Note" operation_id: "CreateProjectNote" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateProjectNote.md" available_via_ai: true - name: "Get A Project Note" operation_id: "GetProjectNote" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetProjectNote.md" available_via_ai: true - name: "Edit A Project Note" operation_id: "EditProjectNote" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditProjectNote.md" available_via_ai: true - name: "Delete A Project Note" operation_id: "DeleteProjectNote" markdown: "https://revcent.com/documentation/markdown/mcp/operation/DeleteProjectNote.md" available_via_ai: true - name: "Search Project Notes" operation_id: "SearchProjectNotes" markdown: "https://revcent.com/documentation/markdown/mcp/operation/SearchProjectNotes.md" available_via_ai: true --- # Projects Projects are durable workspaces inside RevCent. A Project gives a business, initiative, workflow, or AI-enabled process a dedicated place to keep purpose, scope, related RevCent entities, decisions, warnings, follow-up items, and Project Notes together. In plain language: > A Project is the long-term context container for work that should not be forgotten. Projects are especially useful when RevCent work spans more than one session, more than one person, more than one AI interaction, or more than one connected feature. Instead of treating every task as a disconnected action, Projects let RevCent organize work around a durable objective. --- ## Why Projects Are a Feature Projects are a feature because they are created and managed intentionally by a user, AI workflow, MCP client, or external agent. A Project is not the result of a single transaction. It is a reusable organizational layer that can hold context across many RevCent objects and many future interactions. Examples of what a Project can represent: - a business being onboarded into RevCent, - a WooCommerce implementation, - a subscription billing migration, - a payment setup initiative, - a fulfillment setup initiative, - an AI Assistant setup workspace, - an AI Voice Agent setup workspace, - a customer support process, - a revenue recovery initiative, - a chargeback mitigation effort, - a product catalog cleanup, - a shop launch, - an external-agent source of truth, - a long-running operational objective, - a shared notes and decision workspace. The key idea is durability. If future RevCent work would benefit from knowing what was already decided, created, connected, or warned about, a Project is the right place to preserve that context. --- ## Core Purpose The purpose of Projects is to keep related RevCent work together. A Project helps answer questions like: - What is this work for? - Which RevCent objects belong to this effort? - Why was this setup created? - What decisions were already made? - What should future users or AI agents know before making changes? - Which entities are part of the same business, workflow, or initiative? - What follow-up work remains? - What should not be changed without approval? Projects give RevCent a way to organize work around meaning, not just around individual records. A Product can exist on its own. A Payment Profile can exist on its own. A Shop can exist on its own. But a Project can explain why those objects exist together. --- ## Simple Ecosystem Model A Project can be thought of as the organizing layer above many RevCent features. ```text Project -> Project Notes -> Associated RevCent features and records -> Decisions, purpose, warnings, and follow-up context -> Future AI/MCP and user understanding ``` The Project itself stores the main purpose and scope. Project Notes store the ongoing history. Associated entities show what belongs to the Project. Together, they create a relationship graph that future users, AI Assistants, AI Voice Agents, MCP clients, and external agents can understand. --- ## Projects as Context Workspaces Projects are most useful when context matters. A Project can act like a workspace for a specific business or objective. For example, a WooCommerce launch Project might connect: - the Third Party Shop, - Products imported from the shop, - Product Groups used to organize those products, - Subscription Profiles used for recurring products, - Shipping Profiles, - Fulfillment Accounts, - Tax Profiles, - Payment Profiles, - Gateways, - PayPal Accounts, - Email Templates, - SMTP Profiles, - Customer Portal configuration, - Tracking Domains, - Functions, - AI Assistants, - AI Voice Agents, - related Project Notes. Without a Project, those entities may still exist, but the reason they belong together is harder to understand later. With a Project, the relationship graph becomes clear. --- ## Projects and Project Notes Project Notes are the most important related item for Projects. A Project is the container. A Project Note is the durable memory entry inside that container. Project Notes can explain: - what was created, - what was changed, - why the change happened, - which user approved it, - what entity IDs or names were involved, - what assumptions were made, - what problems were found, - what still needs follow-up, - what future AI or users should avoid changing, - how an external agent should behave. In relationship graph terms: ```text Project -> Project Note -> decision / change / finding / warning / follow-up ``` A Project association says, “this object belongs here.” A Project Note explains, “this is why it belongs here.” Both matter. --- ## Why Project Notes Matter Project Notes prevent a Project from becoming just a folder of linked objects. They turn a Project into a living knowledge trail. A good Project Note gives future context that may not be obvious from the associated entities alone. For example: - A Subscription Profile may be associated with a Project, but the note explains that it was created only for one custom billing arrangement. - A Payment Profile may be associated with a Project, but the note explains that routing changes were approved for a specific launch. - A Function may be associated with a Project, but the note explains what external system it sends data to and what should not be changed. - An AI Assistant may be associated with a Project, but the note explains its boundaries and escalation rules. - A Third Party Shop may be associated with a Project, but the note explains product mapping decisions and remaining setup items. This is especially important for AI and external agents, because they need durable context before taking action. --- ## Projects and Associated Entities Projects can be associated with many RevCent entities. This makes a Project a relationship hub across the RevCent ecosystem. A Project may connect to setup and configuration features such as: - Campaigns, - Products, - Product Groups, - Payment Profiles, - Gateways, - Gateway Groups, - PayPal Accounts, - Shipping Profiles, - Fulfillment Accounts, - Subscription Profiles, - Tax Profiles, - Third Party Shops, - Third Party Integrations, - Email Templates, - SMTP Profiles, - Customer Portals, - Tracking Domains, - URL Parameter Sets, - Functions, - Key Values, - AI Assistants, - AI Voice Agents, - BIN Profiles, - Customer Groups. The Project does not replace those entities. It gives them shared context. --- ## Projects and Businesses A Project can represent a specific business being managed in RevCent. This is helpful when one RevCent account supports multiple businesses, brands, stores, campaigns, or initiatives. A business-specific Project can keep that business's RevCent setup together. For example: ```text Acme Skincare RevCent Setup ``` That Project could hold the business purpose, related Campaigns, Products, Shops, Payment Profiles, Gateways, Email Templates, Functions, Tracking Domains, and Project Notes. This prevents unrelated businesses from being mixed together. It also helps AI and MCP avoid applying one business's assumptions to another business. --- ## Projects and WooCommerce / Shops Projects are very useful for Third Party Shops, especially WooCommerce stores. A WooCommerce implementation often includes many connected pieces: - shop connection, - product import or sync decisions, - shipping method mapping, - alternate payment mapping, - PayPal account connection, - subscription billing behavior, - trial behavior, - Customer Portal embedding, - Email Template ownership, - fulfillment setup, - tracking setup, - AI support configuration, - voice support configuration, - Functions for custom logic. A Project can tie all of those together. The Third Party Shop is the storefront connection. The Project is the workspace that explains the full implementation. Project Notes can preserve what was imported, what was mapped, what remains unfinished, and what should be reviewed before future changes. --- ## Projects and AI Assistants Projects are valuable for AI Assistants because they give the assistant durable context. An AI Assistant may need to understand: - which business it supports, - which Products or Shops are in scope, - what actions it is allowed to take, - what actions it should avoid, - which Payment Profiles or Functions are relevant, - which Email Templates are used, - when to escalate, - what previous decisions were made. A Project can store that context through its description, associated entities, and Project Notes. This helps keep AI Assistant behavior grounded in the correct business objective. It also reduces the chance that the assistant treats unrelated RevCent objects as part of the same workflow. --- ## Projects and AI Voice Agents AI Voice Agents can also benefit from Projects. A voice agent may be created for inbound support, outbound recovery, subscription renewal help, shop support, product questions, or operational follow-up. A Project can describe: - the voice agent's purpose, - the business or workflow it supports, - allowed call behavior, - escalation rules, - verification requirements, - related AI Voice Agent records, - related Functions, - related Products, Sales, Subscriptions, or Shops, - notes about testing and changes. This matters because voice workflows often touch customers directly. Project Notes help future users or agents understand what was approved, what should be escalated, and what should not be changed casually. --- ## Projects and Functions Functions often connect RevCent to custom business logic or third-party services. Projects help explain why a Function exists. A Function might: - send Sale information to an external service, - receive webhook data, - enrich Email Template data, - support an AI Assistant tool, - support an AI Voice Agent pre-call workflow, - perform custom payment routing logic, - update Key Values, - connect to a non-native third-party system. The Function itself may show what it does, but the Project can explain the broader reason it exists. Project Notes can record setup decisions, external system names, warnings, and future maintenance guidance. --- ## Projects and Global Features Some RevCent features can affect many customers, transactions, subscriptions, or workflows. Examples include: - Payment Profiles, - Gateways, - Gateway Groups, - Subscription Profiles, - Shipping Profiles, - Tax Profiles, - Email Templates, - SMTP Profiles, - Customer Portals, - Functions, - AI Assistants, - AI Voice Agents. Projects help avoid confusion around these global features. When a global feature is part of a Project, Project Notes should explain whether it is: - specific to one business, - shared across multiple businesses, - temporary, - experimental, - production-ready, - safe to change, - not safe to change without confirmation. This is one of the biggest benefits of Projects. They create a place to preserve the “why” behind important configuration. --- ## Projects and External Agents A Project can serve as a source of truth for an external AI agent, MCP client, or operational assistant. In that case, the Project should explain: - the agent's objective, - what the agent is allowed to do, - what the agent should not do, - which RevCent entities matter, - which notes should be reviewed first, - what safety or escalation rules apply, - what follow-up work exists. Project Notes can then act as the agent's update trail. This makes Projects useful beyond the RevCent web app or API. They become a shared context layer for AI-assisted operations. --- ## Projects and Long-Running Work Some work is not finished in one step. Projects are useful for work that unfolds over time, such as: - onboarding a new store, - launching a new campaign, - setting up subscription billing, - adjusting payment routing, - improving renewal recovery, - building customer support automation, - connecting external services, - cleaning up product catalogs, - migrating fulfillment workflows, - refining AI Assistant behavior, - testing AI Voice Agent scripts. A Project keeps these efforts from becoming scattered across disconnected objects. It gives the effort a name, a purpose, a set of related entities, and a history. --- ## Projects and Relationship Graphing Projects are especially important for relationship graphing because they sit above individual RevCent entities. Most RevCent items and features represent a specific thing: - a Product, - a Shop, - a Payment Profile, - a Function, - an AI Assistant, - a Customer Portal, - a Subscription Profile. A Project represents the reason those things are grouped together. In a relationship graph, Projects help show: - which entities belong to the same business setup, - which entities support the same objective, - which automation pieces belong together, - which shop configuration pieces are related, - which AI tools and voice agents share the same purpose, - which notes explain past decisions, - which entities should be reviewed together before changes. Projects make the ecosystem easier to navigate because they create a purposeful grouping layer. --- ## Project Lifecycle A Project usually follows a simple lifecycle. ```text Create the Project -> define purpose and scope -> associate relevant RevCent entities -> add Project Notes as work happens -> review notes before future changes -> update the Project as scope changes ``` A Project can stay active for as long as the business objective exists. Some Projects may be short-lived, such as a setup or migration initiative. Other Projects may remain long-term, such as a business workspace, AI agent source of truth, or ongoing operational process. --- ## Project Description as the Source of Truth The Project description should be treated as the high-level purpose statement. It should explain: - what the Project is for, - which business, workflow, or objective it covers, - what is in scope, - what is out of scope, - what future users or AI agents should understand, - whether changes should require special approval, - how related entities should be interpreted. A strong Project description makes the whole Project easier to understand. A weak Project description can make future context unclear. Good Project descriptions are specific, plain-language, and durable. --- ## Good Project Names A Project name should be clear enough that someone can understand its purpose from a list. Good names are specific: - `Acme Skincare WooCommerce Launch` - `Acme Skincare Subscription Setup` - `Customer Support AI Assistant Workspace` - `Renewal Recovery Voice Agent Setup` - `Gateway Routing Cleanup` - `Product Catalog Reorganization` - `External Support Agent Source of Truth` Avoid names that are too vague: - `Setup` - `Main` - `Test` - `Changes` - `Stuff` - `Notes` A Project name should help future users and AI choose the right Project quickly. --- ## Benefits Projects provide several ecosystem benefits. They help RevCent users: - organize work around business meaning, - group related RevCent features together, - preserve decisions and context, - reduce repeated discovery work, - avoid mixing unrelated initiatives, - make AI/MCP work more reliable, - keep external agents grounded in the right scope, - document why global configuration exists, - understand what belongs to a business, shop, workflow, or objective, - leave useful context for future users. Projects are especially valuable when RevCent is used as a connected operating system for ecommerce, subscriptions, payments, shops, fulfillment, AI, voice, and automation. --- ## Common Mistakes to Avoid Avoid treating Projects as simple folders. A Project should explain purpose, not just hold associations. Avoid using one generic Project for unrelated businesses or objectives. This can confuse future AI, users, and external agents. Avoid creating associated entities without notes. The association shows what belongs together, but the note explains why. Avoid vague Project names. Names should describe the business, workflow, objective, or agent context. Avoid changing globally impactful entities without reviewing the Project context first. A Project may contain warnings or decisions that matter before changes are made. Avoid deleting Project Notes casually. Project Notes preserve historical context. Editing or clarifying a note is often safer than removing it. --- ## AI/MCP Guidance For AI and MCP use, Projects should be treated as durable context workspaces. Before doing meaningful RevCent setup, review, or modification, AI/MCP should determine whether the work belongs to an existing Project. If a relevant Project exists, AI/MCP should use it. If the work has long-term context and no Project exists, creating a Project may be appropriate. AI/MCP should use Project Notes to preserve important changes, decisions, warnings, and follow-up work. This makes future AI interactions safer and more useful because they can retrieve Project context instead of guessing from incomplete conversation history. Projects should not be used to hide uncertainty. If context is incomplete, Project Notes should say what is known, what is assumed, and what still needs confirmation. --- ## Technical Links - API: `https://revcent.com/docs/api/v2#section-projects` - MCP: `https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md` These technical links are useful for systems that need to create, retrieve, update, associate, or review Projects and Project Notes. The ecosystem purpose of Projects is broader: they help RevCent preserve durable business context and relationships over time. --- ## Relationship Summary | Related area | Relationship to Projects | |---|---| | Project Notes | Store durable memory, decisions, warnings, changes, findings, and follow-up context for the Project. | | RevCent entities | Can be associated with a Project so users and AI know which objects belong to the same business, workflow, or objective. | | AI Assistants | Can use Project context to stay grounded in the right purpose, scope, and constraints. | | AI Voice Agents | Can use Project context to understand allowed behavior, escalation rules, and related workflows. | | Functions | Can be connected to Projects so custom automation has a documented business purpose. | | Third Party Shops | Can be grouped inside Projects to explain shop setup, product mapping, payment mapping, and implementation context. | | Payment and subscription features | Can be associated with Projects to preserve why payment, renewal, shipping, tax, or customer-facing configuration exists. | | External agents | Can treat a Project as a source-of-truth workspace for durable instructions and context. | --- ## Summary Projects are RevCent's durable context workspace feature. They help organize businesses, initiatives, workflows, setups, AI tools, voice agents, external-agent context, and related RevCent entities into a coherent relationship graph. A Project explains the purpose. Associated entities show what belongs to that purpose. Project Notes preserve the history, decisions, warnings, and follow-up work. Together, Projects and Project Notes help RevCent users, AI Assistants, AI Voice Agents, MCP clients, and external agents understand not only what exists, but why it exists and how it should be handled in the future. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.