Setting up your Org in OpsBase it's really simple 🎉 but it is essential for Admins to understand how all the gears fit together on the platform and how they connect to each other.

When going through your basic Org configurations we suggest you perform the below actions in the given order to successfully start using OpsBase:

  • Create at least one Place

  • Create at least one Team and associate it to the existing Place/s

  • Create one or multiple Positions and associate them to a Team/s

  • Create Individual Staff users and associate them to Position/s and all the Places they can work at, for them to then be automatically associated with the relevant Teams

  • Create your first Op and assign it to the Place/s it is available, as well as the Teams and/or Positions responsible for it

It is really important that each individual item is directly linked to the next one.

Essentially, unless you build your Org with the above in mind, you might hit a blocker at some point.

Let me show you exactly what that means, see this short bad 🙅‍♀️ example below:

Staff Users and Teamboards

Configuration of these things will also determine what Ops show up on an Individual Device as opposed to a TeamBoard access:

  • When accessing the Native App with an individual login - using a phone number or email - users will be able to see all the Ops and Issues associated with their personal profile, Position/s and Team/s.

  • However, when using a Teamboard code to access the Native App they will only be able to see Ops and Issues assigned to a specific Team and Place (as configured by the Admin within the Web App). They will not be able to view Ops and Issues assigned to specific Positions or Staff.

Did this answer your question?