Skip to content

Service Provider

A Service Provider is a third party providing a service to an event: a venue, an AV company, a caterer, a translator, a recording crew. Service Providers need to be in the loop for their specific slice of an event — but they should not see the whole event or the delegate list unless they have a reason to.

This role exists at the event and session levels.

What you can see

By default, a Service Provider sees:

  • The event or session page they are attached to.
  • The logistics details relevant to their service — date, venue, technical requirements.
  • Their own tasks.

They typically do not see:

  • The full attendee list (unless the task requires it — for example, catering with dietary requirements).
  • Unrelated content of the event.
  • Tasks for other roles.

The exact permission scoping is enforced via the group role configuration in fedms_federation/config/roles_permissions.yml.

Typical tasks

Service type Typical task
Venue "Confirm room setup", "Confirm catering numbers".
AV company "Test the AV", "Provide the stream URL", "Deliver the recording".
Caterer "Receive dietary list", "Confirm headcount".
Translator "Confirm language pair", "Receive briefing materials".

Tasks are spawned automatically when you are added to an event/session with the Service Provider role, based on the task patterns configured for that event type.

Your dashboard

The dashboard for a Service Provider is intentionally minimal — only the events you are attached to and the tasks you need to complete.

Federation note

Service Providers usually do not run their own FedMS instance. They get a user account on the training company's or event agency's instance and see only what they need.

If your organization works with many event agencies, each will give you a separate account on their instance. (A future "single sign-on across federated FedMS instances" feature would make this smoother — see the Roadmap.)

Next steps