VauPrime DocsOrganizationBranches Management

OrganizationCurrent app behaviorDart-source backed

Branches Management

Understand the current VauPrime branch model. There is no separate branch-creation form in the active VauPrime workflow: creating a new branch uses the same Organization Creation experience used to add another organization/company.

Creation method

Same as Organization Creation

No second branch-specific form to learn

Primary action

Create New Branch

Continue into the standard organization onboarding flow

Plan aware

Branch capacity check

Creation can be limited by the active subscription

After creation

Select & assign

The new organization/branch becomes available for access and user targeting

Important — no separate branch creation screen

The old standalone Add Branch form is not the current VauPrime user flow. From Branches Management, treat “Create New Branch” as the entry point to the normal Organization Creation workflow. The same onboarding screen, validations and organization setup steps are used.

What is Branches Management?

Purpose and current VauPrime behavior.

Branches in VauPrime are additional organization workspaces used when the same business operates more than one location, outlet, office or operating unit.

The current product does not require a separate Add Branch form. A new branch is created with the same Organization Creation onboarding used when adding another company from the organization selector.

This is why the branch guide intentionally does not repeat the old Branch Name / Branch Code / standalone branch-password form. Those controls belonged to an older standalone screen and are not the current creation experience users should follow.

After a branch is available, it can be selected as a Target Organization / Branch when inviting users and assigning role-based access.

Mobile UI structure

What the user sees and what each action does on the compact layout.

Branches page purposeUse the page as the branch entry and guidance surface rather than expecting a second branch-specific data-entry form.

Create New BranchThe primary branch-creation action continues to the normal Organization Creation workflow. Users should see this wording as the branch-specific entry point even though the destination is the shared onboarding experience.

Organization selector relationshipThe current VauPrime organization selector already uses the same onboarding screen when the user chooses Add Company. Branch creation follows this shared model rather than maintaining a separate form.

Creation formOn mobile, complete the same owner, industry, GST/PAN and optional organization-password onboarding documented on the Organization Creation page.

Owner detailsAt least one owner is required. Owner names and 8-digit owner passwords follow the same creation validations as a normal organization.

Industry & taxChoose the correct industry and enable GST only when applicable. Industry-specific requirements continue to apply.

Finish creationComplete onboarding and return to organization selection. The newly created workspace can then be used as the required branch/organization target in supported access-management flows.

Windows UI structure

Desktop layout, lists, tables and actions.

Branches page purposeWindows uses the same branch concept: there is no separate active branch wizard that needs its own form documentation.

Create New BranchUse this branch-specific action to continue into the standard Organization Creation experience.

Desktop organization formThe shared Windows creation flow contains organization name, print name, address, state/country, phone, website, PAN, establishment date, industry, financial-year/currency setup, logo/signature and owner information where applicable.

Owner setupOwner name, phone and 8-digit password use the same validation rules as standard organization creation.

Industry-specific setupRestaurant, Chartered Accountant and other industry-specific requirements continue to come from the shared organization onboarding flow.

After creationOnce created, the branch/company appears in organization selection and can be chosen by Users Management as the Target Organization / Branch for user access.

What is actually configured when creating a branch

Because branch creation reuses Organization Creation, these are shared onboarding concepts rather than a separate branch-only form.

Create New BranchBranch-page action/keyword that sends the user into the shared Organization Creation flow.

Organization / Branch nameUse the location or operating-unit name that should identify this branch in organization selection.

OwnersThe shared creation flow collects owner identity and protected owner access details. Mobile onboarding supports up to five owners.

IndustrySelect the branch’s operating industry so the correct setup and industry-specific fields are prepared.

GST & PANConfigure tax identifiers only when they apply. GSTIN and PAN follow the same validation as Organization Creation.

Organization passwordOptional protected organization access can be enabled in the shared onboarding flow; when enabled the password is 8 digits.

Address / contact / profileWindows full creation includes the organization profile fields used to identify the new branch/location.

Target Organization / BranchAfter creation, Users Management can target the new branch when inviting a user and assigning access.

Create a new branch with the current VauPrime flow

Current user flow from start to completion.

Open Branches Management

Open the Organization section and choose Branches Management.

Choose Create New Branch

This is the branch-specific entry point. Do not look for an old Add Branch tab or separate branch form.

Run the subscription check

VauPrime evaluates branch capacity for the current plan before allowing another branch when a plan limit applies.

Continue to Organization Creation

The same onboarding experience used for a normal additional organization/company is used for the branch.

Enter organization details

Complete the applicable owner, industry, tax, contact and protection fields using the normal Organization Creation rules.

Complete onboarding

Finish creation and return to organization selection.

Use the new branch

The created workspace can be selected for organization/branch access, user invitations and permissions where the product exposes Target Organization / Branch.

Subscription and plan checks

Plan-aware checks that can affect this workflow.

LiteCurrent branch-capacity logic allows up to 1 branch.

EliteCurrent branch-capacity logic allows up to 3 branches.

PrimeCurrent branch-capacity logic allows up to 10 branches.

EnterpriseCurrent branch-capacity logic allows up to 25 branches.

VauOneCurrent branch-capacity logic treats branch creation as unlimited.

Limit reachedWhen the current plan has reached its branch capacity, VauPrime shows an upgrade prompt instead of continuing with another branch.

Validation and common checks

Conditions checked before completing an action.

Branch creation follows Organization Creation validation rather than the removed standalone Add Branch form.

At least one owner is required in mobile onboarding; owner names must be valid and owner passwords are exactly 8 digits.

GSTIN is required when GST is enabled and must be 15 characters; PAN, when entered, must be 10 characters.

If organization-level password protection is enabled, the password must be exactly 8 digits.

Industry-specific required information still applies; for example, a Restaurant setup requires its applicable license information.

If the active subscription has reached branch capacity, create-new-branch should stop at the upgrade flow rather than creating another branch.

Important behavior and notes

Current product behavior worth knowing.

Do not document or train users on the old standalone Add Branch / Branch List tabs as the current VauPrime creation path.

“Create New Branch” is a branch-context navigation label; the actual data-entry experience is the shared Organization Creation screen.

The existing Organization Creation documentation remains the source of truth for the detailed creation form and its mobile/Windows differences.

A branch becomes useful for access control after creation because Users Management can explicitly select a Target Organization / Branch.

Branch plan limits are checked against the active subscription; when capacity is reached, an upgrade prompt is expected.