Skip to main content

New company onboarding

Overview​

Cross-screen roadmap to get a new company up and running in Accelero Visitas — from the initial registration to the point where visitors can check in and approvers can decide on invitations. Each step points to the detailed page of its corresponding screen.

Order matters

Follow the sequence client → company → integration → units → approvers. Skipping steps causes the most common symptoms: invitations with no approver, nothing synchronizes, or a visitor flow without the vehicle choice.

Step by step​

  1. Client — make sure the client that owns the company already exists (the company is linked to a client). See Clients.
  2. Create the company — in Management > Companies, register the company. Set Name, Slug (it becomes the public visitor URL), Latitude/Longitude and Allowed radius (the proximity rule), Logo, and Client. On the Settings tab, decide Is a logistics center (enables the visit type/vehicle choice in the visitor flow), Uses QR Code, and Email notification for approvers. See Companies.
  3. Configure the integration with Accelero — fill in the Integration data (Accelero URL and token, local token) and configure the plugin on the Accelero side (tokens in both directions, AcceleroVisitas URL, event type). See Integration with Accelero.
  4. Units and Departments — register the units manually or use Sync with Accelero to bring them in by External ID. See Units.
  5. Approvers — register the approvers and link them to the units/departments (marking the primary unit when there is more than one). See Approvers.
  6. QR Code / public URL — generate the company QRCode (actions menu in Companies) and validate the public URL derived from the slug.
  7. Validation — run an end-to-end test: a visitor in the public flow (visitor home) and an approver deciding on the invitation (in the app or in the approvers web panel).

Prerequisites​

  • A client registered to link the company to.
  • Integration data for Accelero (URL and tokens) when the company is synchronized with access control.
  • At least one approver linked, otherwise invitations have no one to go to.

Business rules​

  • The slug defines the public URL and must be unique, lowercase, and hyphenated.
  • Latitude/Longitude + Allowed radius govern proximity-based approval.
  • Is a logistics center changes the visitor flow: without it, every visit is assumed to be on foot.
  • Synchronization of units/departments only works after the integration data is filled in and the tokens match those in Accelero.
Note for Integrator Support

Your focus is steps 3 and 4 — integration data consistent with the Accelero plugin and synchronization of units/departments by External ID. Confirm the tokens in both directions and the event type before triggering synchronization.