--- title: "Organizations" description: "A non-technical overview of Organizations in RevCent, focused on how they group sub-user accounts, define web-app visibility boundaries, and primarily restrict Supervisor and Employee access through Campaign association." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/Organization.md" relationships: - name: "Campaign" url: "https://revcent.com/documentation/markdown/ecosystem/feature/Campaign.md" - name: "User" url: "https://revcent.com/documentation/markdown/ecosystem/feature/User.md" technical_links: web_app: "https://kb.revcent.com/management/organization" --- # Organizations Organizations are a web-app-only configurable feature in RevCent used to group sub-user accounts and apply visibility boundaries. An Organization is not required to process sales or use most RevCent features. It is mainly used when a RevCent account has multiple teams, brands, business units, storefronts, or operating groups and needs lower-level users to see only the parts of the account that apply to them. The practical idea is: ```text Organization = sub-user grouping and visibility boundary Campaign association = primary way to restrict Sales, Customers, and related records User = sub-user account assigned to the Organization when applicable ``` Organizations are especially important for Supervisor and Employee users, because those user types are assigned to one or more Organizations and their access can be limited by the Organization's associations and the permissions configured on the user account. --- ## Why Organizations Are a Feature Organizations are a feature because they are configurable account-level structures created and managed by the business inside the RevCent web app. They are not spawned by a single sale, customer action, payment attempt, or AI workflow. Instead, the business creates Organizations intentionally to define how sub-users should be grouped and what those users should be able to see. Conceptually: ```text Business creates Organization ↓ Business associates Campaigns and other account resources ↓ Business assigns Supervisor or Employee users ↓ Those users operate inside the configured visibility boundary ``` This makes Organizations different from items such as customers, transactions, AI threads, or fraud detections. Organizations are durable access and account-structure configuration. --- ## Web-App-Only Configuration Organizations are configured in the RevCent web app. A user can view Organizations from the Organizations area, create a new Organization, and edit an existing Organization's details, associations, and assigned users. This ecosystem document treats Organizations as a web-app-only configurable feature. AI/MCP should understand the concept and respect the visibility model, but should not present Organizations as an API-created or MCP-created object in this documentation. --- ## Technical Links | Area | Link | |---|---| | Web App | `https://kb.revcent.com/management/organization` | --- ## Core Purpose The core purpose of an Organization is to control how sub-user accounts are grouped and what they can see inside the RevCent web app. Organizations are useful when a business wants to answer questions such as: - Which users belong to this team, brand, business, store, or operating group? - Which Campaign-related activity should those users be able to view? - Should this Supervisor manage Employee users inside a specific Organization? - Should this Employee only see activity for a specific Campaign? - Which products, coupons, shops, or metadata should this group be able to access or view? Organizations should be treated as an access-planning feature, not just a label. --- ## Relationship to Campaigns Campaign association is the primary way Organizations restrict visibility for sales, customers, and related commerce records. When one or more Campaigns are selected on an Organization, users assigned to that Organization can be restricted to the records related to those Campaigns. Conceptually: ```text Organization ↓ Associated Campaigns ↓ Supervisor / Employee users assigned to the Organization ↓ Users see Sales, Customers, and related records for those Campaigns ``` This makes Campaign selection one of the most important Organization settings. A Campaign organizes commerce activity. An Organization uses Campaign association to define which portion of that activity lower-level users should be able to see. --- ## Campaign Visibility Restrictions The most important Organization rule is that selecting Campaigns can restrict visibility for users assigned to the Organization. This means Organization users may only be able to view: ```text Sales Customers Transactions Subscriptions Trials Shipping records Chargebacks Fraud detections Other records related to the selected Campaigns ``` This restriction is meant for Supervisor and Employee users. It helps the account owner or administrator separate access across teams, brands, stores, or business units. Important: ```text Do not select Campaigns on an Organization and assign users to that Organization unless Campaign-based visibility restriction is intended. ``` If the goal is only to organize internal account structure without limiting what users can see, Campaign association should be handled carefully. --- ## Relationship to Users Users are the sub-user accounts that can be assigned to an Organization. RevCent user types include: | User Type | Organization Required? | General Role | |---|---:|---| | Account Owner | No | Primary account holder with full access. | | Administrator | No | Higher-level user with broad administrative access, except restricted account-management actions. | | Supervisor | Yes | Lower-level management user assigned to one or more Organizations. | | Employee | Yes | Lower-level user assigned to one or more Organizations. | Account owners and administrators are not assigned to Organizations. Supervisors and Employees must be placed in one or more Organizations. Their access is shaped by the Organization they belong to, the Organization's associations, the abilities enabled for the user, and the permissions assigned to the user. --- ## Organization Users An Organization can have Supervisor and Employee users attached to it. Supervisor and Employee users are the users most affected by Organization visibility boundaries. A Supervisor may be given abilities to create or modify Employee users inside their own Organization. Employee users are more limited and are configured with specific permissions. This makes the Organization a boundary for both visibility and team structure: ```text Organization = team / business unit boundary Supervisor = manages or works within that boundary Employee = works within that boundary Permissions = what actions the user can perform Associations = what records or resources the user can see ``` --- ## User Abilities and Permissions Organization assignment is only one part of sub-user access. Supervisor and Employee users can also have abilities and permissions configured. Examples of user access controls include: - Whether the user can view list pages. - Whether a Supervisor can create Employee accounts within their Organization. - Whether a Supervisor can modify Employee accounts within their Organization. - Which permission types and methods are enabled for the user. Organization associations answer: "Which part of the account can this user see?" User permissions answer: "What can this user do?" Both matter. --- ## Organization Associations Organization associations group related RevCent resources and, in some cases, apply visibility restrictions. Common Organization associations include: | Association | Main Purpose | |---|---| | Campaign | Primary visibility boundary for Sales, Customers, and related commerce records. | | Product Group | Controls which product groups and associated products users can view. | | Coupon | Controls which coupons users can view or apply. | | Metadata Group | Controls which metadata users can view. | | Third Party Shop | Controls which shops users can view for filtering and selection. | | Tracking Domain | Groups tracking domains with the Organization. | | AdWords Account | Groups AdWords accounts with the Organization. | | Organization Preset | Controls which presets are available to users in the Organization. | Not every association works the same way. Campaign association is the key association for sales/customer visibility boundaries. --- ## Campaign vs Other Associations Campaign associations should not be confused with other Organization associations. A Third Party Shop association may control shop visibility for filtering and selection, but it does not restrict visibility of sales, transactions, and related commerce records for that shop. If the goal is to restrict users so they only see sales and customers for a specific shop or business unit, the business should use Campaign association. A Product Group association controls product-group and product visibility. It does not apply visibility restrictions to sales, subscriptions, or related commerce records. A Metadata Group association controls which metadata users can view. This is separate from Campaign visibility. A Tracking Domain association groups tracking domains with the Organization, but is not the primary mechanism for restricting sales/customer visibility. The safe rule is: ```text Use Campaign associations for Sales, Customers, and related commerce visibility. Use other associations for their specific resource visibility or availability behavior. ``` --- ## Organizations vs Campaigns Organizations and Campaigns are related, but they are not the same thing. | Concept | Main Purpose | Typical Use | |---|---|---| | Organization | Group sub-users and define visibility boundaries. | Team, business unit, or staff access separation. | | Campaign | Organize sales, customers, and commerce activity. | Brand, store, funnel, or sales-flow segmentation. | A Campaign answers: ```text Which business activity does this record belong to? ``` An Organization answers: ```text Which users should be grouped together, and what should they be able to see? ``` The two work together when Campaigns are attached to an Organization to define what lower-level users can view. --- ## Organizations vs Users An Organization is not the same as a User. A User is an account someone logs into. An Organization is the grouping and visibility boundary that certain user types belong to. Conceptually: ```text User = person/account that logs into RevCent Organization = boundary that groups Supervisor and Employee users Campaign association = primary data visibility filter for that boundary ``` Users can have permissions. Organizations have associations. The final access experience is shaped by both. --- ## When Organizations Are Useful Organizations are useful when a RevCent account needs to separate access by team, store, brand, department, or business unit. Common examples: ```text A brand has multiple internal teams and each team should only see its own Campaign activity. A business has customer support employees who should only see assigned Campaigns. A supervisor should manage employees for one operating unit. A company has multiple storefronts inside one RevCent account and wants staff separated by store. A business wants employees to see only specific products, coupons, or metadata groups. ``` Organizations are optional. A single-business account with only account owner or administrator users may not need them. --- ## Creating an Organization Creating an Organization starts with the basic details: ```text Name Description Status ``` After the Organization is created, the business can edit the Organization to add associations and assign users. A good Organization name should make the team or business boundary obvious. Good examples: ```text Acme Skincare Support Team Brand A Employee Group Wholesale Operations Team Subscription Support Organization ``` Avoid vague names: ```text Org 1 Main Team Test ``` The Organization name should help future users and AI/MCP understand what staff group or access boundary it represents. --- ## Editing an Organization Editing an Organization can change how users experience RevCent. Important editable areas include: ```text Organization details Organization associations Organization users ``` Changes to Campaign associations can affect which sales, customers, and related records Supervisor and Employee users can view. Changes to assigned users can move a person into or out of a visibility boundary. Changes to other associations can affect which resources those users can access or select. Because of that, Organization edits should be treated as access-control changes, not cosmetic changes. --- ## Safe Setup Pattern A safe Organization setup should usually follow this pattern: ```text 1. Decide why the Organization exists. 2. Decide which Supervisor and Employee users should belong to it. 3. Decide which Campaigns define the records those users should see. 4. Add Campaign associations only when visibility restriction is intended. 5. Add other associations only when they are needed. 6. Configure user abilities and permissions separately. 7. Review the setup before relying on the Organization for live staff access. ``` This helps avoid accidentally hiding records from users or exposing records they should not see. --- ## Visibility Design Checklist Before using an Organization for staff access, the business should know: ```text Which users belong in the Organization? Are those users Supervisors or Employees? Which Campaigns should those users be able to see? Should users see all Campaign activity or only selected Campaigns? Do Product Group, Coupon, Metadata Group, or Third Party Shop restrictions also matter? Should any Supervisor be allowed to create or modify Employee users? Which permissions should each user have? ``` The most important question is: ```text Which Campaigns should define this Organization's sales/customer visibility boundary? ``` --- ## AI and MCP Guidance AI/MCP should treat Organizations as a web-app-only concept used for staff grouping and visibility planning. When explaining or planning Organizations, AI/MCP should emphasize: ```text Organizations group sub-user accounts. Supervisor and Employee users are assigned to Organizations. Campaign association is the primary way to restrict Sales, Customers, and related commerce visibility. Other associations have narrower purposes. Organization changes can affect what lower-level users can see. ``` AI/MCP should not casually recommend Campaign association unless the user wants visibility restrictions. AI/MCP should also avoid treating a Third Party Shop association as enough to restrict all sales/customer activity for that shop. If sales/customer visibility restriction is the goal, Campaign association is the primary setting to consider. --- ## Common Mistakes ## Mistake: Treating Organizations as Required Organizations are optional. They are useful when the business needs sub-user grouping and visibility boundaries. A simple account with no lower-level users may not need Organizations. ## Mistake: Confusing Organizations With Campaigns An Organization groups users and sets visibility boundaries. A Campaign organizes sales, customers, and related commerce activity. Use Campaigns to define the business data segment. Use Organizations to define which lower-level users can see that segment. ## Mistake: Using Third Party Shop Association for Sales Visibility A Third Party Shop association controls shop visibility for filtering and selection. It does not apply sales/customer visibility restrictions for that shop. Use Campaign association when the goal is to restrict sales, transactions, customers, and related commerce records. ## Mistake: Selecting Campaigns Without Intending Restrictions Selecting Campaigns on an Organization can restrict users assigned to that Organization. Do not associate Campaigns casually. ## Mistake: Ignoring User Permissions Organization association controls what records or resources a user can see. User permissions control what actions the user can perform. Both need to be configured intentionally. --- ## Summary Organizations are RevCent's web-app-only feature for grouping sub-user accounts and controlling visibility boundaries. They are optional and mainly useful when a RevCent account has Supervisor or Employee users who should only see specific parts of the business. The most important concept is: ```text Campaign association is the primary way Organizations restrict visibility for Sales, Customers, and related commerce records. ``` Users, especially Supervisors and Employees, are assigned to Organizations. Campaigns, Product Groups, Coupons, Metadata Groups, Third Party Shops, Tracking Domains, AdWords Accounts, and Organization Presets can be associated with Organizations, but Campaign association is the key visibility boundary for commerce records. Used carefully, Organizations help a business separate teams, brands, stores, departments, or operating groups inside one RevCent account while keeping lower-level user access aligned with the correct Campaign activity. --- 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.