Body
Overview
Adding a department to TeamDynamix is much lighter than your first IT rollout, because IT has already built the foundation: authentication, the people import, and the platform setup. The ten questions below are the ones admins most often ask before they bring HR, Facilities, Finance or another team on board. Each answer says what to expect and what to decide up front, so you can move forward with confidence.
1. What does our global admin still own once a department has its own app admin?
Giving a department app admin rights doesn't take your global admins out of the picture. A few platform-level tasks stay with them, and naming who does what before kickoff is the biggest factor in a smooth expansion.
| Usually the global admin |
Usually the department app admin |
| Create the department's apps and grant app admin rights |
Configure forms, ticket types, statuses and templates |
| Create groups and assign the right global security roles |
Build the department's services and service catalog |
| Create desktop templates |
Write knowledge base articles |
| Set up email monitoring and other organization-wide settings |
Build workflows, reports and the department portal |
A few habits help:
- Bring IT to the kickoff, even if they only stay involved at a high level.
- Name a backup app admin in each department, so the work doesn't stall if the lead admin leaves.
- Agree on a governance model. Some organizations use a community of practice, where admins from each department meet to keep naming, reporting and the end-user experience consistent.
2. What is shared across departments, and what does each department set up on its own?
Anything set up at the organization level is shared by every department, and much of it is already in place because IT went first. That includes authentication (SSO) and the people import. Each department then builds what lives inside its own apps.
| Shared across all departments |
Set up per department |
| People, accounts/departments and locations |
Ticket types, statuses and forms |
| Groups, priorities and type categories |
Workflows and automation rules |
| Days off (organization holidays) |
Templates, reports and desktops |
| Time and expense types |
Email intake for the department |
| The service catalog and knowledge base (each department adds its own services and articles) |
Asset tracking, if the department needs it |
Ask for a department-specific readiness plan that marks each action item as "IT / global admin" or "department." Department leads often get confused when training covers items IT already configured, and a split plan clears that up on day one.
3. Should the department get its own app, and its own portal?
Most departments get their own ticketing app, and often their own asset app. That gives each team its own space to configure without touching IT's setup. Decide this early, because applications can't be deleted once they're created.
For the portal, the approach that works well for most organizations is a single front door:
- One portal where end users find every department's services.
- Top-level catalog categories by department, so people can find HR or Facilities at a glance.
- Shortcuts for crossover services, where someone might look under one department for a service another department provides.
A separate portal per department is also an option when a team needs its own branding or audience.
4. How will requests come in: email, forms or both?
Plan for both, and steer people toward forms over time. Forms collect the right details up front and cut down on back-and-forth.
- Give each department its own intake email address. One shared mailbox is hard to route reliably to several departments.
- Replace unstructured email with forms wherever you can, but keep them short so people still use the portal.
- Keep email for people who can't sign in, such as outside vendors or tenants.
- Avoid public, no-login forms. They can be indexed by search engines and attract spam or malicious attachments.
5. How much effort is it, and can we do it ourselves?
Adding departments takes far less effort than the first rollout, because they build on the foundation IT already set up. Most organizations learn enough from their IT implementation to roll out later departments with much less help.
Choose the level of support that fits your team:
- Do it yourselves. Your admins use what they learned in the IT rollout, plus TeamDynamix training and the knowledge base.
- Guided help. A TeamDynamix consultant coaches the department's app admin through setup and best practices.
- Strategy first. If you're planning several departments, an ESM strategy session helps you set the governance model and rollout order before anyone builds.
6. Where should we start, and how simple should the first version be?
Start with one department that has a willing leader and a clear pain point, such as requests arriving by email or paper forms. Keep the first version simple: it's much easier to add complexity later than to take it out.
- Up to 20 services. You can add more after go-live.
- Name an owner for each service, so it's clear who picks up a request the moment it's submitted.
- Skip the extras at first. SLAs, advanced workflows, cascading attributes and automation rules can come in a later phase.
- Write services in the requester's language, not the department's internal jargon. Ask a trusted end user to review the catalog before go-live.
- Help non-technical staff get comfortable. Short tip sheets for daily tasks, simple desktops and a clear date when the old inbox or spreadsheet retires all speed adoption.
- Get leaders aligned, for example the HR and IT leaders sharing the same goal for the rollout.
7. Should we build in sandbox or in production?
Decide before anyone starts building. There's no bulk copy from sandbox to production, so a department built entirely in sandbox has to be rebuilt.
| Sandbox is best for |
Production is best for |
| Learning and practicing |
The real configuration you plan to keep |
| Testing bulk imports (people, departments, locations) |
Email monitoring, which doesn't run in sandbox |
| Trying out forms and workflows |
New applications, which can't be deleted once created |
Sandbox is refreshed from production on the first business Monday of January, April, July and October, which overwrites anything built there. Build the real setup in production and keep it hidden from end users until go-live.
8. How do we keep department data private while departments still work together?
Each department's apps are separate, so you control who can see their tickets. Sensitive teams such as HR or Public Safety can keep tickets and knowledge base articles visible only to their own groups. Plan up front for how those teams will handle sensitive information that arrives by email, since department app admins usually can't delete tickets.
Departments can still share work when a process crosses teams:
- Misrouted requests. A ticket sent to the wrong department can be moved to the right app. Custom fields don't carry over one-to-one, but their values are kept as a comment.
- Employee onboarding and offboarding. One request from HR can create tickets and tasks for IT, Facilities and Security.
- Workflow handoffs. A workflow step in one app can create a ticket in another department's app.
These cross-department processes are often what convinces leadership that ESM is worth it.
9. Who needs a license?
Staff who work tickets in the department need a Work Management license. People who only submit requests or check status through the client portal do not.
One detail to plan for: client portal users can be given permission to view reports, but they only see the report data if their security role has a Technician or Enterprise license type. Decide early which department managers need that view.
Your account manager can help you size licenses department by department so there are no surprises.
10. Will the AI features work for a new department on day one?
Plan for them to grow into it. AI features learn from a department's own tickets and knowledge base, and a brand-new department starts with neither.
- Write the department's top knowledge base articles before go-live.
- Use consistent services and categories, so early tickets are easy to learn from.
- Bring over past requests where that makes sense, rather than starting from zero.
- Turn on AI for the department once it has a few months of ticket history.
Next steps
- Pick your first department and name its leader, app admin and a backup admin.
- List up to 20 services that department handles today.
- Agree on who owns what between your global admins and the department app admin.
- Decide on apps, portal layout and the department's intake email address.
- Decide what to build in production and what to prototype in sandbox.
- Schedule a call with your account team to plan support level and licenses.