This is complicated, can you summarize it for me?

Remember, access to data in Connections[Beta] is driven by movement affiliation. If a user has access to a movement, they can see all the Inbox, Contact, and Event & Group records in that movement. A team of 15 staff members could be responsible for 7 movements. But, these movements can all be set up differently and each staff doesn’t necessarily need access to every movement all the time. Connections[Beta] was built to allow for such flexibility. To summarize, Movements can be set up 3 different ways:

  • Standard (most common)- One movement, one location
  • Metro (less common) – One movement, multiple locations
  • Parent (rare) – Multiple movements, one location, one Fall survey

Affiliation to these movements can change from person to person on your staff and student leadership teams. It’s built to help mirror how ministry is actually done on the ground. As you think about setting up movements in Connections[Beta], here are some good questions to ask: For my regular student leadership meetings, which students are present from which campuses? Do we decide things together or separately? Who needs access to the information in this movement?

To make modifications or ask clarifying questions, please email help@cru.org.