Skip to main content

Organizations Management

As a tenant administrator, you shape how people and work are grouped inside Booga Enterprise. Organizations give you named units—departments, regions, projects, or any structure that fits your business—that you can use to assign users and align with how resources are scoped in the product. This guide describes the administrator’s workflow: seeing what already exists, creating and editing organizations, building a parent–child hierarchy, and assigning users from User Management. End-user documentation on what organizations mean day to day and how scoped resources behave lives in the user guides; here the focus stays on setup and governance. For broader product documentation, see the Booga Enterprise documentation site.

Overview​

Organizations let you group users and scope resources within your tenant. As an admin, you create organizations, define their hierarchy, assign users, and manage membership.

Each organization has an identity you control: a name, a description that helps others understand its purpose, and optionally a parent organization when it should sit under another unit in the tree. Users are not locked to a single organization—they can belong to more than one when your processes require matrix-style membership. That flexibility matters when someone spans teams or when you reuse the same person across divisions without duplicating accounts.

You will encounter organizations in two primary places: the Resources Overview on the Admin Portal home page, which surfaces a quick picture of all units, and User Management, where you connect people to those units through the Organization Assignment flow. Together, these views help you keep structure visible at a glance and keep membership accurate over time.

Prerequisites​

Before you rely on organizations for access or reporting alignment, confirm the following:

  • You hold an Admin or SuperUser role (or equivalent tenant-level administrative access) so you can create organizations and change assignments.
  • You have a practical picture of how your company actually works—teams, regions, legal entities, or delivery groups—so you name and nest organizations in a way that stays stable as the business evolves.

If you are unsure whether your role includes organization administration, compare your account with another administrator’s or review your tenant’s role documentation before you restructure hierarchy or bulk-assign users.

Security Considerations​

Important: Organization changes affect resource access scoping and user visibility. When you add or remove users from an organization, or when you move an organization under a different parent, you may change who can see which resources and how broadly data appears in scoped experiences. Treat hierarchy and membership updates as security-relevant actions: coordinate with owners of sensitive data, communicate planned changes, and verify outcomes in a lower-risk environment or with a small pilot group when your policies require it.

Viewing Organizations​

On the Admin Portal home page, find the Resources Overview panel. The Organizations section lists the organizational units that exist in your tenant today.

Each entry is presented as a card-style row you can scan quickly. You see the organization name, a description preview so you can tell similar-sounding units apart, and an indicator when the row represents a sub-organization—that is, a unit that sits under a parent in the hierarchy rather than at the top level. Use this section when you want a dashboard-level answer to “what do we call our units?” and “which ones are nested?” without opening a separate screen for every single check.

When the list is long, the area scrolls so the home page remains usable. If you have just created or renamed an organization and do not see it yet, refresh the page once the platform has finished saving (see Troubleshooting if the new unit still does not appear).

Creating Organizations​

When you create a new organization, you define how it will appear to administrators and how it fits into your tenant’s structure.

Start from the workflow your tenant uses to add organizations (typically reachable from User Management or your tenant’s organization administration area, depending on product packaging). Provide a name that is unique enough to avoid confusion with sibling units—clarity beats brevity when two departments share a similar acronym.

Add a description that states the unit’s purpose in plain language. New administrators and auditors will thank you when they can read intent without asking around. If the organization should roll up under another, set a parent organization so the platform records the relationship from day one. If you leave parent empty, the organization sits at the root of your tenant’s org tree until you edit it later.

Save your changes and confirm the new unit appears under Organizations in Resources Overview or in your organization list, depending on where you verify.

Building Hierarchies​

Organizations support parent–child relationships. When you set a parent organization, you create a sub-organization under that parent. The hierarchy is not decorative: it supports how you group people and how scoped resources and visibility align with real reporting lines or project boundaries.

A well-designed tree enables:

  • Cascading resource scoping — Depending on product behavior, child organizations may inherit or aggregate scope from ancestors so that policies and content align with the tree you maintain.
  • Hierarchical user grouping — You can reflect departments, regions, or programs without flattening everything into one long list of unrelated names.
  • Departmental isolation — Distinct branches help separate concerns where teams should not see each other’s scoped assets by default.

You build the tree by choosing parents when you create organizations or by editing an existing organization to point to a new parent. Keep the structure intentional: frequent moves confuse users and can disrupt access expectations. When you must move a branch, communicate the change and validate that critical memberships still match the new structure.

Assigning Users​

Membership is where structure meets people. From User Management, locate the user you need to attach to one or more organizational units, then use the Organization Assignment dialog to select the organizations that apply.

You can assign a user to multiple organizations when their role spans teams or when matrix reporting applies. The dialog is the right place to add or remove those links without guessing which field on a profile might be obsolete. After you save, confirm the user’s organizations match what you expect—especially after reorganizations or role changes.

If you onboard many users at once, establish a repeatable pattern: name the organizations first, then assign users in batches by department or project so you do not leave half of a team on the old structure.

Managing Organizations​

After creation, you continue to maintain organizations as the business changes.

  • Edit name and description when branding, mergers, or internal renaming require it. Update descriptions at the same time so Resources Overview previews stay truthful.
  • Change parent organization when you restructure—moving a sub-organization under a different division, for example. Plan these moves carefully to avoid surprising users whose scoped resources follow the tree.
  • Review member counts and assigned resources where the product surfaces them, so you can spot empty shells, overloaded units, or misassignments before they become support tickets.

If your workflow includes retiring an organization, follow your tenant’s process for decommissioning (archiving users, reassigning resources, and removing the unit) rather than deleting in isolation.

Best Practices​

  • Design the hierarchy before you create organizations at scale. A short whiteboard or spreadsheet of parent–child names and owners saves painful renames later.
  • Keep hierarchy depth manageable—often two to three levels unless your business truly needs deeper nesting. Shallow trees are easier to explain and to audit.
  • Align organization names with actual business structure so administrators and end users recognize units without a translation layer.
  • Review membership periodically—for example quarterly or after reorganizations—to ensure Organization Assignment still reflects who works where.

Troubleshooting​

An organization does not appear after you saved it.
Refresh the Admin Portal page. If it still does not show, wait a moment for background processing, then refresh again. Confirm you are viewing the correct tenant and that your role still allows viewing the full organization list.

You cannot assign users to organizations.
Verify you have administrative permissions for User Management and organization assignment. If another admin recently changed your role, sign out and back in, then retry. Escalate to a SuperUser if your tenant policy reserves certain actions for elevated roles.

You see hierarchy conflicts or unexpected parent relationships.
Ensure you are not creating circular references—an organization cannot ultimately be its own ancestor. If the UI prevents a parent choice, pick a different parent or flatten the branch. If behavior seems inconsistent after a move, coordinate with peers to confirm whether any automation or integration also updates organization links.

For related end-user concepts and how scoped resources behave in the product, see the user guides referenced from the Booga Enterprise documentation site.

⏱️ Read time: 10 minutes | 📊 Difficulty: intermediate