Below are some examples of structures where clients may feel they require divisions – with an analysis of appropriateness.
Franchises
Bob owns a cleaning company "Cloud Clean", which he has recently franchised. While each of the franchisees are responsible for the day to day running of their own businesses, part of the contract is that Bob will specify the way his company is represented in the market. Bob would also like to monitor the performance and effectiveness of each of the franchises and allocate the sales inquiries to the correct franchise. Bob holds the domain for @cloudclean.com and all the franchises will use this.
This environment is a good reason to use Divisions.
Bob will be able to create the applicable Action Types, with documents, branding, knowledge base and wiki; thus being assured that Cloud Clean is represented the way Bob prescribes in the market place. Each of the franchises will be able to run their own business as an individual entity – without seeing records not belonging to their franchise. Sales Inquiries will come into the Root Division and Bob will allocate to the franchise on creation of the action. Bob is able to compile views and reports based on the actions of all Franchises. Each user will have an email address @cloudclean.com.
The Legal Company | Services Company
Common email domain
Steven is practise manager at a Law Firm "You Matter". While the Law firm has a number of lawyers, runs a trust account and does client billing; the non-lawyer employees are employed by a separate company "Legal Services Inc" which also runs the practise and bills the law firm for its services. These companies are separate entities as a clear division is required for compliance reasons. All employees of both companies use an email address of @you matter.com.
This environment is a good reason to use Divisions.
The staff in the services company will be able to see the matters in the legal company – thus giving the ability to create documents etc. The accounting will be separated into each company.
Email Domain not common
...
The Branch | Department Environment (Cost Centres)
With Accounting
...
| Info | ||
|---|---|---|
| ||
| This same scenario can be applied where a company runs multiple departments or cost centers. |
Without Accounting
...
| Info | ||
|---|---|---|
| ||
| Creating permissions for users who may be able to see actions in some divisions and not others is possible; however, it can be tricky to unwind if roles and |or structure change. If using this method, ensure adequate testing is done around each of the roles |
...
| Info |
|---|
See updated article in Actionstep help Center: https://support.actionstep.com/hc/en-us/articles/360053566414 |