Internal Teams

• What does Usherfly look like for internal teams?

  Instead of writing "read this, meet this person, request access to that system" emails for every new team member, you build the flow once. The invite goes out; they complete it at their own pace.

• What's the simplest first flow I can run?

  Team intro (INFO) → Channel join and tool access (TASK) → IT access request (TASK, Task Owner: IT) → Access confirmed (CHECKPOINT). Four steps.

• How do I structure steps for internal team onboarding?

  INFO for team intro, TASK for channel joins and access requests, CHECKPOINT for access confirmation, DOCUMENT for technical docs, FORM for getting-to-know-you surveys.

• How do I invite new team members?

  Use "Add onboardee" — enter name and work email. For multiple people, upload a CSV.

• What's the freemium limit and when should I upgrade?

  1 concurrent active onboarding (finish one, free the slot); admins and templates are unlimited. Move to Growth (10) when you need to bring more people on board at once.

• What's the most common pitfall for internal teams?

  Skipping the CHECKPOINT after an access request step. Don't assume "submitted the request = access granted." Always add a CHECKPOINT after the TASK.

• Is the flow different for freelancers or contractors?

  Use the same flow type; add an NDA or service agreement to the E-SIGN step, then a CHECKPOINT for "Contract signed, cleared to proceed."