Employee Feeds import workforce data and can publish lifecycle events that trigger automated experiences. Restrict access so that only authorized administrators can create, configure, and manage feeds and their connections.
Who typically needs access
| Audience | What they usually need |
| IT and integration teams | Create feeds, manage connections, configure mappings, and monitor synchronization activity. |
| HR and People Operations | Review synchronized employee data outcomes and support feed requirements. |
| Experience and process owners | Configure or request lifecycle events that trigger journeys and workflows. |
What access should cover
Depending on their responsibilities, authorized administrators may need permission to:
- Create and edit Employee Feeds.
- Choose connectors and configure connections.
- Configure field mappings.
- Configure lifecycle events.
- Preview mappings and run sample synchronizations.
- View synchronization history, record outcomes, and event delivery logs.
- Pause, resume, and replay feeds.
- Manage the connections used by Employee Feeds.
Note: Users who don't manage feeds shouldn't be able to change feed configuration, connections, or event publishing settings.
Recommended practices
- Restrict connection management to integration administrators.
- Limit production feed configuration changes to a small group of authorized administrators.
- Review access when people change roles or responsibilities.
- Remove access when it is no longer required.
Security considerations
- Polling feeds authenticate through Applaud connections.
- Spreadsheet and webhook feeds use dedicated endpoints rather than a vendor API connection.
- Uploaded files are scanned before they are processed.
- Feeds can pause automatically after repeated failures.