# Pyn Help > Help and education for the Pyn app: set up your workspace, run flows, and understand what your employees see. Pyn Help is the public help and education site for Pyn, the app HR teams use to run employee moments (onboarding, change, check-ins and celebrations) over Slack, Microsoft Teams and email. Every page below is also available as plain markdown at the same path with a `.md` suffix, and https://support.pynhq.com/llms-full.txt holds every page in one file. https://support.pynhq.com/api/stories.json lists the pages with their frontmatter, https://support.pynhq.com/api/media.json the screenshots and videos, and https://support.pynhq.com/for-agents/ explains the conventions. ## Getting started - [Getting started](https://support.pynhq.com/getting-started/): What Pyn is, how a flow works, and the path from a new workspace to your first live automation. (markdown: https://support.pynhq.com/getting-started.md) - [Launch first-day onboarding end to end](https://support.pynhq.com/getting-started/tutorial-launch-first-day-onboarding/): Build a start-date flow with a pre-start email, a day-one welcome and a manager nudge, test it on yourself, review the first enrollments and switch it to Automated. (markdown: https://support.pynhq.com/getting-started/tutorial-launch-first-day-onboarding.md) - [Set up your workspace in 30 minutes](https://support.pynhq.com/getting-started/tutorial-set-up-your-workspace/): From an empty workspace to a live flow: bring in employees, connect a channel, brand your emails, invite your team and turn on one automation. (markdown: https://support.pynhq.com/getting-started/tutorial-set-up-your-workspace.md) - [Communicate the rollout](https://support.pynhq.com/getting-started/communicate-the-rollout/): Decide what changes when Pyn starts sending, who needs to know, and how to announce it so the first messages are expected rather than a surprise. (markdown: https://support.pynhq.com/getting-started/communicate-the-rollout.md) - [Invite your team](https://support.pynhq.com/getting-started/invite-your-team/): Invite a colleague to your Pyn workspace by email, choose their role, resend an invitation, change a role later or remove someone's access. (markdown: https://support.pynhq.com/getting-started/invite-your-team.md) - [Plans and what each unlocks](https://support.pynhq.com/getting-started/plans/): The plans a Pyn workspace can be on, what the app does differently on each, how add-ons show their availability, and where to ask for an upgrade. (markdown: https://support.pynhq.com/getting-started/plans.md) - [Roles and permissions](https://support.pynhq.com/getting-started/roles-and-permissions/): The four workspace roles, which navigation items and actions each one unlocks, who can change whose role, and how the labels differ between screens. (markdown: https://support.pynhq.com/getting-started/roles-and-permissions.md) - [Views, filters, search and export](https://support.pynhq.com/getting-started/views-filters-search-and-export/): The control bar on every table and board in Pyn: the view menu, Filters, Sort, Find, Metrics, Save View, and the three kinds of export. (markdown: https://support.pynhq.com/getting-started/views-filters-search-and-export.md) ## For employees and managers - [For employees and managers](https://support.pynhq.com/for-employees/): What it means when a message from Pyn arrives in your inbox, Slack or Teams, how to act on it, how to reply, and what Pyn records about you. (markdown: https://support.pynhq.com/for-employees.md) - [For managers](https://support.pynhq.com/for-employees/for-managers/): What Pyn sends you about the people who report to you, why a reminder or an escalation arrives, and how to nominate a buddy. (markdown: https://support.pynhq.com/for-employees/for-managers.md) - [Pick a buddy](https://support.pynhq.com/for-employees/for-managers/pick-a-buddy/): Nominate a buddy for a new starter from the people picker in the Slack message Pyn sends you; the choice is written to the new starter's record and starts the buddy's own messages. (markdown: https://support.pynhq.com/for-employees/for-managers/pick-a-buddy.md) - [What nudges and escalations look like](https://support.pynhq.com/for-employees/for-managers/what-nudges-and-escalations-look-like/): A reminder is the original message sent again a set number of days later; an escalation is a short generated notice to a manager, skip-level manager, HRBP or buddy saying who has not completed what. (markdown: https://support.pynhq.com/for-employees/for-managers/what-nudges-and-escalations-look-like.md) - [Accept a calendar invitation](https://support.pynhq.com/for-employees/accept-a-calendar-invitation/): Pyn adds you as a guest to an existing event in your company's Google Calendar or Outlook calendar, so the invitation arrives from the calendar, not from Pyn. (markdown: https://support.pynhq.com/for-employees/accept-a-calendar-invitation.md) - [Acknowledge a message](https://support.pynhq.com/for-employees/acknowledge-a-message/): Select the button in a message from Pyn to confirm you have read a policy, finished a task or opened a page; Pyn records it and stops any reminders. (markdown: https://support.pynhq.com/for-employees/acknowledge-a-message.md) - [Answer a form or poll](https://support.pynhq.com/for-employees/answer-a-form-or-poll/): Answer a Pyn form or poll inside the Slack message it arrived in, or on the respond page an email button opens, and see Submitted when it is recorded. (markdown: https://support.pynhq.com/for-employees/answer-a-form-or-poll.md) - [Privacy and your data](https://support.pynhq.com/for-employees/privacy-and-your-data/): What Pyn holds about you comes from your company's HR system; what it records about a message is whether it was delivered, whether you opened a link and whether you acted; only your company's Pyn users see either. (markdown: https://support.pynhq.com/for-employees/privacy-and-your-data.md) - [The reader and respond pages](https://support.pynhq.com/for-employees/public-pages/): Two pages a Pyn message can open without a sign-in: the reader page shows an article the People team wrote, and the respond page takes a form or poll answer. (markdown: https://support.pynhq.com/for-employees/public-pages.md) - [Reply to a message](https://support.pynhq.com/for-employees/reply-to-a-message/): Where a reply goes depends on the channel and the sender: a person's mailbox or Slack account, a company address, or the Pyn app, which no person reads. (markdown: https://support.pynhq.com/for-employees/reply-to-a-message.md) - [Why you received a message from Pyn](https://support.pynhq.com/for-employees/why-you-received-a-message/): A message from Pyn was written by your People team, sent from a person or address they chose, and timed by a date on your employee record such as your start date or anniversary. (markdown: https://support.pynhq.com/for-employees/why-you-received-a-message.md) ## Home - [Home](https://support.pynhq.com/home/): Home is where you land after signing in: a greeting, the date and a checklist of setup steps that tick themselves off as your workspace comes together. (markdown: https://support.pynhq.com/home.md) - [Complete the getting-started checklist](https://support.pynhq.com/home/complete-the-getting-started-checklist/): Work through the cards on Home, see what each one opens and what makes it tick itself off, and dismiss the guide card when you no longer need it. (markdown: https://support.pynhq.com/home/complete-the-getting-started-checklist.md) - [Navigate Pyn](https://support.pynhq.com/home/navigate-pyn/): The left navigation on every page: what each item opens, which items each role sees, how Search works and what the Notices dot means. (markdown: https://support.pynhq.com/home/navigate-pyn.md) ## AI - [AI](https://support.pynhq.com/ai/): Pyn AI, in preview: a home page, a Context section with employees, countries and departments, and an Agents section with a skill catalogue and a run log. The preview shows a sample organisation, not your workspace's data. (markdown: https://support.pynhq.com/ai.md) - [Agents](https://support.pynhq.com/ai/agents/): The Agents section of the Pyn AI preview: a Skills table of 22 skills tied to journey moments, two of them enabled, and a Runs log with the time, duration and result of each run. (markdown: https://support.pynhq.com/ai/agents.md) - [Skill catalogue](https://support.pynhq.com/ai/agents/reference-skill-catalogue/): Every skill in the Pyn AI preview, grouped by the part of the employee journey it serves, with its journey moment, owner, whether it is enabled, and what its description says it does. (markdown: https://support.pynhq.com/ai/agents/reference-skill-catalogue.md) - [Context](https://support.pynhq.com/ai/context/): The Context section of the Pyn AI preview: tables of employees, countries and departments from a sample organisation, and the Employee Context page that gathers the signals and suggested actions for one person and their reports. (markdown: https://support.pynhq.com/ai/context.md) ## Journey - [Journey](https://support.pynhq.com/journey/): The Journey is a board of the employee lifecycle: categories hold moments, and each moment links to the flows and content that serve it. (markdown: https://support.pynhq.com/journey.md) - [Build your journey map](https://support.pynhq.com/journey/tutorial-build-your-journey-map/): A 30-minute walk from the starter map to a prioritised plan: trim it, mark your gaps, pick the moments that matter and put flows behind them. (markdown: https://support.pynhq.com/journey/tutorial-build-your-journey-map.md) - [Add a category](https://support.pynhq.com/journey/add-a-category/): Add a column to the Journey board for a stage of the employee experience your map does not cover yet, then name and colour it. (markdown: https://support.pynhq.com/journey/add-a-category.md) - [Add a moment](https://support.pynhq.com/journey/add-a-moment/): Add a moment card to a Journey category straight from the board, then open it to describe the experience and set its properties. (markdown: https://support.pynhq.com/journey/add-a-moment.md) - [Archive a moment](https://support.pynhq.com/journey/archive-a-moment/): Take a moment you do not run off the Journey board, and bring it back later from the Archived view. (markdown: https://support.pynhq.com/journey/archive-a-moment.md) - [Attach a flow or content to a moment](https://support.pynhq.com/journey/attach-a-flow-to-a-moment/): From a moment's panel, see the flows and content that serve it and add more from the template catalogue. (markdown: https://support.pynhq.com/journey/attach-a-flow-to-a-moment.md) - [Export the map as an image](https://support.pynhq.com/journey/export-the-map/): Download the Journey board you are looking at, filters and all, as a PNG for a slide deck or a leadership update. (markdown: https://support.pynhq.com/journey/export-the-map.md) - [Filter the map](https://support.pynhq.com/journey/filter-the-map/): Narrow the Journey board to the moments that match a Current State, Priority, Level of Effort or Department, or find a moment by name. (markdown: https://support.pynhq.com/journey/filter-the-map.md) - [Read journey metrics](https://support.pynhq.com/journey/read-journey-metrics/): Put a number on every moment card: employees in the moment, deliveries, clicks or actions over the last 30 days to 12 months. (markdown: https://support.pynhq.com/journey/read-journey-metrics.md) - [Reorder moments and categories](https://support.pynhq.com/journey/reorder-moments-and-categories/): Drag moments within or between categories, and drag categories along the board, to put the Journey in the order employees live it. (markdown: https://support.pynhq.com/journey/reorder-moments-and-categories.md) - [Save a view](https://support.pynhq.com/journey/save-a-view/): Keep a filtered, measured Journey board as a view of your own, then rename, duplicate, switch the view type or archive it. (markdown: https://support.pynhq.com/journey/save-a-view.md) - [Set a moment's properties](https://support.pynhq.com/journey/set-moment-properties/): Record how well you cover a moment today, how much effort it takes to improve, its priority, the team responsible and who owns it. (markdown: https://support.pynhq.com/journey/set-moment-properties.md) - [Moment properties](https://support.pynhq.com/journey/reference-moment-properties/): Every property on a journey moment, with its options, plus the fields on a category and the three seeded Journey views. (markdown: https://support.pynhq.com/journey/reference-moment-properties.md) ## Library - [Library](https://support.pynhq.com/library/): The Library holds the content employees read and the media your messages embed: write and publish once, link from any flow. (markdown: https://support.pynhq.com/library.md) - [Content](https://support.pynhq.com/library/content/): Content is a page an employee reads from a button in a message. Write it once, publish it, and every step that links to it shows the latest version. (markdown: https://support.pynhq.com/library/content.md) - [Archive content](https://support.pynhq.com/library/content/archive-content/): Remove a piece of content from the Library's views when you no longer send it, and bring it back if you need it again. (markdown: https://support.pynhq.com/library/content/archive-content.md) - [Create content](https://support.pynhq.com/library/content/create-content/): Start a new piece of library content, write its title and body, give it a Journey moment, and let it autosave as a draft. (markdown: https://support.pynhq.com/library/content/create-content.md) - [Find content](https://support.pynhq.com/library/content/find-content/): Narrow the Content view to one Journey moment, search titles with Find, switch to a table, and save the result as a view. (markdown: https://support.pynhq.com/library/content/find-content.md) - [Publish content](https://support.pynhq.com/library/content/publish-content/): Publish the current draft of a piece of content as a new version that every linked step shows, or discard the draft and go back to the published version. (markdown: https://support.pynhq.com/library/content/publish-content.md) - [Restore a previous version](https://support.pynhq.com/library/content/restore-a-previous-version/): Open an earlier published version of a piece of content from History, read it, and make it the published version again. (markdown: https://support.pynhq.com/library/content/restore-a-previous-version.md) - [Link to content from a message](https://support.pynhq.com/library/content/use-content-in-a-step/): Add a button to a flow step's message that opens a piece of library content, with a label and style of your choice and optional action tracking. (markdown: https://support.pynhq.com/library/content/use-content-in-a-step.md) - [Content states and versions](https://support.pynhq.com/library/content/reference-content-states/): What draft, published, previous version and archived mean for library content, how versions are created, and which actions each state offers. (markdown: https://support.pynhq.com/library/content/reference-content-states.md) - [Media](https://support.pynhq.com/library/media/): Media is the images, video and files you upload once and embed in messages and content; every upload is scanned before it can be used. (markdown: https://support.pynhq.com/library/media.md) - [Insert media in a message](https://support.pynhq.com/library/media/insert-media-in-a-message/): Add an image, GIF or video to a message or piece of content, from your computer or from the Library, and align it. (markdown: https://support.pynhq.com/library/media/insert-media-in-a-message.md) - [Upload media](https://support.pynhq.com/library/media/upload-media/): Add an image, video or file to the Library from the Media view, wait for the malware scan, and check its details. (markdown: https://support.pynhq.com/library/media/upload-media.md) - [Media types and scan states](https://support.pynhq.com/library/media/reference-media-types/): The file types the Library accepts, what the media panel shows, and what the Scanning, Clean, Infected and Error scan states mean. (markdown: https://support.pynhq.com/library/media/reference-media-types.md) ## Directory - [Directory](https://support.pynhq.com/directory/): Directory is the people side of Pyn: every employee the workspace knows about, the groups they belong to, and the demographics those groups are built from. (markdown: https://support.pynhq.com/directory.md) - [Demographics](https://support.pynhq.com/directory/demographics/): A demographic is an employee property Pyn turns into groups, one per value. Five come with every workspace; add more from the properties your sources supply. (markdown: https://support.pynhq.com/directory/demographics.md) - [Archive a demographic](https://support.pynhq.com/directory/demographics/archive-a-demographic/): Retire a demographic you no longer group by, and bring it back later if you need it. (markdown: https://support.pynhq.com/directory/demographics/archive-a-demographic.md) - [Create a demographic](https://support.pynhq.com/directory/demographics/create-a-demographic/): Turn an employee property into groups, one per value, so flows can target by Job Class, Work Office or any yes/no field your HRIS supplies. (markdown: https://support.pynhq.com/directory/demographics/create-a-demographic.md) - [Employee Groups](https://support.pynhq.com/directory/employee-groups/): A group is a saved set of employees that an automation or a step can send to. Pyn keeps most groups up to date for you; a static group is the one you manage by hand. (markdown: https://support.pynhq.com/directory/employee-groups.md) - [Create a filter group](https://support.pynhq.com/directory/employee-groups/create-a-filter-group/): Save an audience as a group: lifecycle stages plus the groups to include and exclude. Pyn keeps its members current. (markdown: https://support.pynhq.com/directory/employee-groups/create-a-filter-group.md) - [Create a relationship group](https://support.pynhq.com/directory/employee-groups/create-a-relationship-group/): Group everyone who has, or lacks, a manager, buddy, mentor or HRBP, or everyone who is one, so a flow can reach them or a report can find the gaps. (markdown: https://support.pynhq.com/directory/employee-groups/create-a-relationship-group.md) - [Create a static group](https://support.pynhq.com/directory/employee-groups/create-a-static-group/): Build a group from named people: search for them, paste their email addresses, or upload a file of addresses. (markdown: https://support.pynhq.com/directory/employee-groups/create-a-static-group.md) - [How audiences match](https://support.pynhq.com/directory/employee-groups/how-audiences-match/): How Pyn combines an audience's lifecycle stages, included groups and excluded groups: groups with the same parent match any one of them, groups with different parents must all match, and an exclusion always wins. (markdown: https://support.pynhq.com/directory/employee-groups/how-audiences-match.md) - [Group types](https://support.pynhq.com/directory/employee-groups/reference-group-types/): The five kinds of employee group, how each decides its members, when it is re-evaluated, and the groups every workspace starts with. (markdown: https://support.pynhq.com/directory/employee-groups/reference-group-types.md) - [Employees](https://support.pynhq.com/directory/employees/): Every current, upcoming and inactive employee, with a profile that merges what each of your sources knows about them. (markdown: https://support.pynhq.com/directory/employees.md) - [Add an upcoming employee](https://support.pynhq.com/directory/employees/add-an-upcoming-employee/): Add one new joiner by hand from the Upcoming view so their preboarding starts before they are in your HRIS. (markdown: https://support.pynhq.com/directory/employees/add-an-upcoming-employee.md) - [Export employees](https://support.pynhq.com/directory/employees/export-employees/): Export an Employees table view to CSV and collect the file from Notices. (markdown: https://support.pynhq.com/directory/employees/export-employees.md) - [Find an employee](https://support.pynhq.com/directory/employees/find-an-employee/): Open one person's profile from anywhere in Pyn with Search, or narrow the Employees list with Find and Filters. (markdown: https://support.pynhq.com/directory/employees/find-an-employee.md) - [Fix a missing manager, time zone or email](https://support.pynhq.com/directory/employees/fix-missing-details/): Why a profile shows a blank manager, time zone or email, which source Pyn takes each value from, and how to put it right. (markdown: https://support.pynhq.com/directory/employees/fix-missing-details.md) - [Read an employee profile](https://support.pynhq.com/directory/employees/read-an-employee-profile/): What each tab of an employee's profile shows: their details and relations, the groups they are in, their enrollments, deliveries and outstanding actions, and the sources behind the record. (markdown: https://support.pynhq.com/directory/employees/read-an-employee-profile.md) - [Upload employees from a spreadsheet](https://support.pynhq.com/directory/employees/upload-employees-from-a-spreadsheet/): Load or update your employees from a CSV, XLS or XLSX file through the Employee File integration, and read the result. (markdown: https://support.pynhq.com/directory/employees/upload-employees-from-a-spreadsheet.md) - [Employee properties](https://support.pynhq.com/directory/employees/reference-employee-properties/): Every field on an employee, the relations between employees, the external ids that tie a profile to its sources, how the lifecycle stage is decided and how a time zone is resolved. (markdown: https://support.pynhq.com/directory/employees/reference-employee-properties.md) - [Your first employee upload and groups](https://support.pynhq.com/directory/tutorial-first-upload-and-groups/): A 25-minute walk from a spreadsheet to an audience: upload your people, check the profiles Pyn built, add a joiner by hand, then create the static and filter groups your first automation will target. (markdown: https://support.pynhq.com/directory/tutorial-first-upload-and-groups.md) ## Flows - [Flows](https://support.pynhq.com/flows/): Automations, campaign templates, forms and polls: everything Pyn sends to employees and everything it collects from them. (markdown: https://support.pynhq.com/flows.md) - [Automations](https://support.pynhq.com/flows/automations/): An automation enrols employees when its trigger fires, filters them with an audience and runs a published sequence of steps relative to a reference date. (markdown: https://support.pynhq.com/flows/automations.md) - [Tutorial: birthdays and anniversaries](https://support.pynhq.com/flows/automations/tutorial-birthdays-and-anniversaries/): Set up yearly work-anniversary and birthday automations that give managers a week's notice and celebrate the person on the day, with milestone years handled separately. (markdown: https://support.pynhq.com/flows/automations/tutorial-birthdays-and-anniversaries.md) - [Tutorial: buddy programme](https://support.pynhq.com/flows/automations/tutorial-buddy-programme/): Run an onboarding buddy programme in Pyn, where the manager nominates a buddy through a form, the buddy is briefed the moment they are chosen, and both sides are checked on through the first month. (markdown: https://support.pynhq.com/flows/automations/tutorial-buddy-programme.md) - [Tutorial: new-manager flow](https://support.pynhq.com/flows/automations/tutorial-new-manager-flow/): Support a first-time manager through their first four weeks with a sequence triggered by their first direct report, and brief their own manager on how to help. (markdown: https://support.pynhq.com/flows/automations/tutorial-new-manager-flow.md) - [Tutorial: offboarding flow](https://support.pynhq.com/flows/automations/tutorial-offboarding-flow/): Build an offboarding automation from the termination date that briefs the manager, walks the leaver through their last two weeks, raises the access ticket and follows up after they have gone. (markdown: https://support.pynhq.com/flows/automations/tutorial-offboarding-flow.md) - [Tutorial: pre-boarding to a personal email](https://support.pynhq.com/flows/automations/tutorial-pre-boarding-to-a-personal-email/): Build a pre-boarding automation that reaches new starters at their personal address in the week before they begin, and nudges their manager to be ready on day one. (markdown: https://support.pynhq.com/flows/automations/tutorial-pre-boarding-to-a-personal-email.md) - [Archive an automation](https://support.pynhq.com/flows/automations/archive-an-automation/): Retire an automation so it enrols nobody and leaves the Automations list, while enrollments already in progress run to completion. (markdown: https://support.pynhq.com/flows/automations/archive-an-automation.md) - [Assign an automation to a moment](https://support.pynhq.com/flows/automations/assign-an-automation-to-a-moment/): Attach an automation to a moment on your journey map so it is grouped with that moment in the Automations table and listed on the moment's Flows tab. (markdown: https://support.pynhq.com/flows/automations/assign-an-automation-to-a-moment.md) - [Change the mode of an automation](https://support.pynhq.com/flows/automations/change-the-mode/): Move an automation between Automated, Verification, Manual and Inactive, or archive it, from the mode button in the editor. (markdown: https://support.pynhq.com/flows/automations/change-the-mode.md) - [Choose a trigger](https://support.pynhq.com/flows/automations/choose-a-trigger/): Open the Select Trigger dialog, pick the family that matches the moment and swap the trigger on an existing automation. (markdown: https://support.pynhq.com/flows/automations/choose-a-trigger.md) - [Configure a date trigger](https://support.pynhq.com/flows/automations/configure-a-date-trigger/): Set when a date trigger fires relative to the employee's date, how often it repeats, and understand what the reference date will be. (markdown: https://support.pynhq.com/flows/automations/configure-a-date-trigger.md) - [Configure a group change trigger](https://support.pynhq.com/flows/automations/configure-a-group-change-trigger/): Start an automation when an employee enters or leaves one of the groups you choose, such as a department, a location or a static list. (markdown: https://support.pynhq.com/flows/automations/configure-a-group-change-trigger.md) - [Configure a recurring trigger](https://support.pynhq.com/flows/automations/configure-a-recurring-trigger/): Run an automation on a timetable, daily, weekly, monthly or yearly, from a start date and time in a time zone you choose, for everyone in the audience. (markdown: https://support.pynhq.com/flows/automations/configure-a-recurring-trigger.md) - [Configure a team change trigger](https://support.pynhq.com/flows/automations/configure-a-team-change-trigger/): Use the Buddy Assigned, Promoted to Manager, Change of Manager, Change of Location and Connected to Slack triggers, which fire the moment a relationship on the employee record changes. (markdown: https://support.pynhq.com/flows/automations/configure-a-team-change-trigger.md) - [Configure an employee property trigger](https://support.pynhq.com/flows/automations/configure-an-employee-property-trigger/): Start an automation from any date, text or yes/no property on the employee record, including custom fields synced from your HRIS. (markdown: https://support.pynhq.com/flows/automations/configure-an-employee-property-trigger.md) - [Create an automation](https://support.pynhq.com/flows/automations/create-an-automation/): Start a new automation from a trigger in the picker or from a ready-made template in the catalogue, then open it in the editor. (markdown: https://support.pynhq.com/flows/automations/create-an-automation.md) - [Duplicate an automation](https://support.pynhq.com/flows/automations/duplicate-an-automation/): Copy an automation, with its trigger, audience, steps and journey moment, into a new inactive draft you can change independently. (markdown: https://support.pynhq.com/flows/automations/duplicate-an-automation.md) - [Enroll from a spreadsheet](https://support.pynhq.com/flows/automations/enroll-from-a-spreadsheet/): Upload a mail merge spreadsheet to enrol many people at once, each with their own reference date and with extra columns available as custom tokens in the messages. (markdown: https://support.pynhq.com/flows/automations/enroll-from-a-spreadsheet.md) - [Export the Flows list](https://support.pynhq.com/flows/automations/export-the-flows-list/): Download the Automations table as a CSV file, with the columns and rows you see, from the view menu's Export Data action. (markdown: https://support.pynhq.com/flows/automations/export-the-flows-list.md) - [Handle late enrollments](https://support.pynhq.com/flows/automations/handle-late-enrollments/): Decide what happens when someone is enrolled after one or more steps were already due, whether by sending them at once, skipping them or reviewing them by hand. (markdown: https://support.pynhq.com/flows/automations/handle-late-enrollments.md) - [Manually enroll employees](https://support.pynhq.com/flows/automations/manually-enroll-employees/): Put chosen employees into an automation yourself, with a reference date you set, by searching, pasting email addresses or uploading a file. (markdown: https://support.pynhq.com/flows/automations/manually-enroll-employees.md) - [Move an enrollment to a new start date](https://support.pynhq.com/flows/automations/move-an-enrollment-to-a-new-start-date/): When a start date changes after someone is enrolled, stop the current enrollment and re-enrol them against the new date without sending anything twice. (markdown: https://support.pynhq.com/flows/automations/move-an-enrollment-to-a-new-start-date.md) - [Prevent repeat enrollments](https://support.pynhq.com/flows/automations/prevent-repeat-enrollments/): Read and understand the re-enrollment timeout on a trigger, which stops the same employee being enrolled again when data changes or a trigger fires twice. (markdown: https://support.pynhq.com/flows/automations/prevent-repeat-enrollments.md) - [Publish an automation](https://support.pynhq.com/flows/automations/publish-an-automation/): Publish a draft so the trigger runs against it, and choose whether enrollments still running on the previous version move to the new one. (markdown: https://support.pynhq.com/flows/automations/publish-an-automation.md) - [Set the audience for an automation](https://support.pynhq.com/flows/automations/set-the-audience/): Limit who a trigger enrols by lifecycle stage and by included and excluded groups, and preview the people who match before you publish. (markdown: https://support.pynhq.com/flows/automations/set-the-audience.md) - [Sort the Flows list](https://support.pynhq.com/flows/automations/sort-the-flows-list/): Reorder the Automations table by journey order, by what needs publishing, by status or by title for the rest of your session. (markdown: https://support.pynhq.com/flows/automations/sort-the-flows-list.md) - [Trigger a flow from a form submission](https://support.pynhq.com/flows/automations/trigger-a-flow-from-a-form-submission/): Start an automation the moment a published form is submitted, with the person who answered it as the principal. (markdown: https://support.pynhq.com/flows/automations/trigger-a-flow-from-a-form-submission.md) - [Use a flow without a trigger](https://support.pynhq.com/flows/automations/use-a-flow-without-a-trigger/): Build an automation that only runs when you enrol people yourself, or one that an external system enrols through the API. (markdown: https://support.pynhq.com/flows/automations/use-a-flow-without-a-trigger.md) - [Automation and enrollment states](https://support.pynhq.com/flows/automations/automation-and-enrollment-states/): The modes an automation can be in, how versions work, and the states an enrollment, an enrollment step and a delivery pass through from creation to completion. (markdown: https://support.pynhq.com/flows/automations/automation-and-enrollment-states.md) - [Scheduling internals](https://support.pynhq.com/flows/automations/scheduling-internals/): How Pyn turns a trigger and a reference date into enrollments and send times, including trigger windows, reference date adjustment, recurrence years, cadence, minimums and time zones. (markdown: https://support.pynhq.com/flows/automations/scheduling-internals.md) - [Trigger catalogue](https://support.pynhq.com/flows/automations/trigger-catalogue/): Every trigger in the Select Trigger dialog and the template catalogue, with its description as shown in the app, what it watches, its default offset, recurrence, window and re-enrollment timeout. (markdown: https://support.pynhq.com/flows/automations/trigger-catalogue.md) - [Campaign Templates](https://support.pynhq.com/flows/campaign-templates/): Dated communications that run on a calendar rather than on an employee's lifecycle: campaign templates you enrol people into, and campaigns you build directly on the Activity calendar. (markdown: https://support.pynhq.com/flows/campaign-templates.md) - [Holidays and observances for the year](https://support.pynhq.com/flows/campaign-templates/tutorial-holidays-and-observances/): Build next year's calendar of holiday greetings and observance notes in about 45 minutes: public holidays from the catalogue, your own observances as one campaign, and a manager note for the days that need one. (markdown: https://support.pynhq.com/flows/campaign-templates/tutorial-holidays-and-observances.md) - [A performance review cycle](https://support.pynhq.com/flows/campaign-templates/tutorial-performance-review-cycle/): Run a review cycle as one campaign: eight short messages over three and a half weeks that tell employees what to do and when, give managers what they need, and thank everyone at the end. About an hour. (markdown: https://support.pynhq.com/flows/campaign-templates/tutorial-performance-review-cycle.md) - [Add a campaign template](https://support.pynhq.com/flows/campaign-templates/add-a-campaign-template/): Add a ready-made campaign template from the catalogue, such as a country's public holidays for the year, so it appears under Campaign Templates ready to enrol people into. (markdown: https://support.pynhq.com/flows/campaign-templates/add-a-campaign-template.md) - [Create a campaign](https://support.pynhq.com/flows/campaign-templates/create-a-campaign/): Build a campaign from scratch on the Activity calendar: name and date it, add email, Slack or channel steps on their own dates, choose the recipients for each, and set the steps to Automated. (markdown: https://support.pynhq.com/flows/campaign-templates/create-a-campaign.md) - [Duplicate a campaign](https://support.pynhq.com/flows/campaign-templates/duplicate-a-campaign/): Run last year's campaign again: copy it with a new title and reference date, shift every step to match, and choose whether to keep the recipients. (markdown: https://support.pynhq.com/flows/campaign-templates/duplicate-a-campaign.md) - [Enroll employees in a campaign](https://support.pynhq.com/flows/campaign-templates/enroll-employees-in-a-campaign/): Use a campaign template: pick its milestones and steps, choose the employees and groups, decide whether to verify first, and confirm. Each milestone becomes a campaign on the Activity calendar. (markdown: https://support.pynhq.com/flows/campaign-templates/enroll-employees-in-a-campaign.md) - [Reschedule a step on the calendar](https://support.pynhq.com/flows/campaign-templates/reschedule-a-step-on-the-calendar/): Move a campaign step to another day by dragging it on the month calendar, or change its date, time and time zone in the step panel. (markdown: https://support.pynhq.com/flows/campaign-templates/reschedule-a-step-on-the-calendar.md) - [Campaign states](https://support.pynhq.com/flows/campaign-templates/reference-campaign-states/): What a campaign and each of its steps can be: a campaign is paused, pending or complete, and a step is Draft, Manual, Automated, Sending or Complete. (markdown: https://support.pynhq.com/flows/campaign-templates/reference-campaign-states.md) - [Cohort Templates](https://support.pynhq.com/flows/cohort-templates/): Rules that decide which employees an automation enrols and when. (markdown: https://support.pynhq.com/flows/cohort-templates.md) - [Forms](https://support.pynhq.com/flows/forms/): Structured questions you put inside a message: text, checkboxes, Likert scales, a buddy or mentor picker. Answers are recorded against the employee, exportable, able to start a flow, and acceptable from another system through a webhook. (markdown: https://support.pynhq.com/flows/forms.md) - [A buddy selection form that triggers a flow](https://support.pynhq.com/flows/forms/tutorial-buddy-selection-form/): In about 40 minutes: build a form with a Buddy field, send it to the manager in Slack a week before a start date, write the buddy onto the new starter's record, thank the manager through a form-triggered flow, and brief the buddy the moment they are chosen. (markdown: https://support.pynhq.com/flows/forms/tutorial-buddy-selection-form.md) - [Build a form](https://support.pynhq.com/flows/forms/build-a-form/): Create a form in Flows, add and configure its fields, preview it as a respondent will see it, and publish it so it can be embedded in a message. (markdown: https://support.pynhq.com/flows/forms/build-a-form.md) - [Create a webhook](https://support.pynhq.com/flows/forms/create-a-webhook/): Let another system submit a form on an employee's behalf: add a webhook to the form, choose which HRIS id identifies the employee, mint the secret once, and read the log of what arrived. (markdown: https://support.pynhq.com/flows/forms/create-a-webhook.md) - [Embed a form in a message](https://support.pynhq.com/flows/forms/embed-a-form-in-a-message/): Put a published form or poll into an email, Slack direct message or channel post from the editor's Widgets menu, with a button style and action tracking. (markdown: https://support.pynhq.com/flows/forms/embed-a-form-in-a-message.md) - [Review and export submissions](https://support.pynhq.com/flows/forms/review-and-export-submissions/): Read the answers to a form or poll in its Activity drawer, open any submission, and download every non-test submission as a CSV with one row per person. (markdown: https://support.pynhq.com/flows/forms/review-and-export-submissions.md) - [Trigger a flow from a submission](https://support.pynhq.com/flows/forms/trigger-a-flow-from-a-submission/): Make a form the start of an automation: when someone submits it, they are enrolled with the submission date as the reference date, so you can thank them, route a request or follow up. (markdown: https://support.pynhq.com/flows/forms/trigger-a-flow-from-a-submission.md) - [Form field types](https://support.pynhq.com/flows/forms/reference-form-field-types/): The six field types a form or poll can hold, what each collects, whether it can be required, and how it renders in Slack, in email and in the CSV export. (markdown: https://support.pynhq.com/flows/forms/reference-form-field-types.md) - [Webhook API](https://support.pynhq.com/flows/forms/reference-webhook-api/): The inbound webhook on a form: endpoint, bearer secret, JSON body with subject_id and fields, idempotency key, the two responses, the once-per-employee rule and every code the log can record. (markdown: https://support.pynhq.com/flows/forms/reference-webhook-api.md) - [Polls](https://support.pynhq.com/flows/polls/): A one-click question inside a message: a Likert scale or a yes/no that records the moment it is clicked, for a weekly pulse or a quick reaction to an event. (markdown: https://support.pynhq.com/flows/polls.md) - [Run a quick poll](https://support.pynhq.com/flows/polls/run-a-quick-poll/): Create a one-question poll, publish it, drop it into a Slack or email step, and read the results as they arrive. (markdown: https://support.pynhq.com/flows/polls/run-a-quick-poll.md) - [Steps and messages](https://support.pynhq.com/flows/steps/): Anatomy of a step in an automation or campaign: the step types you can add, the drawer's Configure, Audience, Reminders and Advanced tabs, and how a step becomes a delivery. (markdown: https://support.pynhq.com/flows/steps.md) - [Add a button to a message](https://support.pynhq.com/flows/steps/add-a-button-to-a-message/): Make a message actionable with a Link Button, a Link To Library Content button or an embedded form, and track who acts on it so reminders and escalations can follow. (markdown: https://support.pynhq.com/flows/steps/add-a-button-to-a-message.md) - [Add a direct message step](https://support.pynhq.com/flows/steps/add-a-direct-message-step/): Send a Slack direct message from an automation or campaign: choose the sender, the person it goes to and the time, then write it with tokens. (markdown: https://support.pynhq.com/flows/steps/add-a-direct-message-step.md) - [Add an email step](https://support.pynhq.com/flows/steps/add-an-email-step/): Send an email from an automation or campaign: pick the mailbox it comes from, the recipient and Cc, the subject and the body, then test it on yourself. (markdown: https://support.pynhq.com/flows/steps/add-an-email-step.md) - [Add escalations](https://support.pynhq.com/flows/steps/add-escalations/): When an actionable message is still not actioned after a number of days, notify someone else, such as the recipient's manager, with a short notice that says what is outstanding and since when. (markdown: https://support.pynhq.com/flows/steps/add-escalations.md) - [Add reminders](https://support.pynhq.com/flows/steps/add-reminders/): Send up to three follow-ups to the recipient of an actionable message, a chosen number of days after it was delivered, that stop the moment they act. (markdown: https://support.pynhq.com/flows/steps/add-reminders.md) - [Add to a channel](https://support.pynhq.com/flows/steps/add-to-a-channel/): Put the employee into a Slack channel automatically on a day of their journey, for example #new-starters on day one or #managers when they are promoted. (markdown: https://support.pynhq.com/flows/steps/add-to-a-channel.md) - [Choose a sender](https://support.pynhq.com/flows/steps/choose-a-sender/): Pick the identity a step sends from: Pyn Bot or a personal Slack account, a Google Workspace or Microsoft 365 mailbox, a verified email address on your domain, or a conditional sender that picks one per recipient. (markdown: https://support.pynhq.com/flows/steps/choose-a-sender.md) - [Choose recipients and Cc](https://support.pynhq.com/flows/steps/choose-recipients-and-cc/): Pick who a step goes to: the employee at their work or personal address, their manager, skip-level manager, buddy or HRBP, a group, a channel or a custom email address, plus up to three Cc recipients. (markdown: https://support.pynhq.com/flows/steps/choose-recipients-and-cc.md) - [Create a conditional sender](https://support.pynhq.com/flows/steps/create-a-conditional-sender/): Send one step from different senders depending on who receives it, with ordered audience rules and a fallback, so regional HR leads sign their own region's messages. (markdown: https://support.pynhq.com/flows/steps/create-a-conditional-sender.md) - [Deactivate link and media unfurling](https://support.pynhq.com/flows/steps/deactivate-unfurling/): Stop Slack expanding links and media into previews under a step's message, so a direct message or channel post keeps the layout you wrote. (markdown: https://support.pynhq.com/flows/steps/deactivate-unfurling.md) - [Format a message](https://support.pynhq.com/flows/steps/format-a-message/): Use the message editor: headings, lists, links and alignment, tokens that fill in names and dates, images, files and video, the Mention Principal pill in Slack, and Raw HTML for a designed email. (markdown: https://support.pynhq.com/flows/steps/format-a-message.md) - [Invite to a calendar event](https://support.pynhq.com/flows/steps/invite-to-a-calendar-event/): Add the employee, or their manager or buddy, to a recurring Google or Outlook calendar event from a step, such as the weekly new-starter welcome or a 1:1. (markdown: https://support.pynhq.com/flows/steps/invite-to-a-calendar-event.md) - [Post to a channel](https://support.pynhq.com/flows/steps/post-to-a-channel/): Announce a new starter, an anniversary or an event in a public Slack channel from a step, with the employee mentioned by name. (markdown: https://support.pynhq.com/flows/steps/post-to-a-channel.md) - [Preview and send a test](https://support.pynhq.com/flows/steps/preview-and-send-a-test/): Read a step as a particular employee, with tokens, sender and recipient resolved, then send it to yourself in Slack or email before you publish. (markdown: https://support.pynhq.com/flows/steps/preview-and-send-a-test.md) - [Raise a ticket](https://support.pynhq.com/flows/steps/raise-a-ticket/): Create a Jira issue from a step, such as an IT equipment request a week before a start date or an access-removal ticket on someone's last day. (markdown: https://support.pynhq.com/flows/steps/raise-a-ticket.md) - [Schedule a step](https://support.pynhq.com/flows/steps/schedule-a-step/): Set when a step sends: the offset from the reference date, the time of day, the recipient's or the workspace's time zone, the days of the week, what happens on a weekend and whether an overdue step is skipped. (markdown: https://support.pynhq.com/flows/steps/schedule-a-step.md) - [Set a step audience](https://support.pynhq.com/flows/steps/set-a-step-audience/): Send one step to only some of the people enrolled in an automation, for example a benefits email to US employees only, without splitting the flow in two. (markdown: https://support.pynhq.com/flows/steps/set-a-step-audience.md) - [Delivery statuses](https://support.pynhq.com/flows/steps/reference-delivery-statuses/): What each status on a message, a step and an enrollment means, from Draft and Scheduled through Delivered, Clicked and Actioned to Bounced, Invalid and Skipped, and what you can do about each. (markdown: https://support.pynhq.com/flows/steps/reference-delivery-statuses.md) - [Step options](https://support.pynhq.com/flows/steps/reference-step-options/): Every field a step can carry, by step type, in plain words: schedule, audience, recipient, sender, message, reminders, escalations and the type-specific settings for calendar, channel and ticket steps. (markdown: https://support.pynhq.com/flows/steps/reference-step-options.md) - [Tokens](https://support.pynhq.com/flows/steps/reference-tokens/): Every token you can put in a message, what Pyn fills it with, the text it falls back to when the value is missing, and how dates and names are formatted. (markdown: https://support.pynhq.com/flows/steps/reference-tokens.md) ## Activity - [Activity](https://support.pynhq.com/activity/): Activity is the record of what Pyn has sent and what it is about to send: every enrollment, every step, every delivery, and the actions people were asked to complete. (markdown: https://support.pynhq.com/activity.md) - [Actions](https://support.pynhq.com/activity/actions/): Every delivery that asked someone to do something, with who was asked, what for, and whether they have done it. (markdown: https://support.pynhq.com/activity/actions.md) - [Track actions](https://support.pynhq.com/activity/actions/track-actions/): List the actions people have been asked to complete, narrow to the ones still outstanding, and export the list with your filters applied. (markdown: https://support.pynhq.com/activity/actions/track-actions.md) - [Enrollments](https://support.pynhq.com/activity/enrollments/): An enrollment is one employee in one automation, or one run of a campaign. Open it to see every step, what has sent and what is still to come. (markdown: https://support.pynhq.com/activity/enrollments.md) - [Open an enrollment](https://support.pynhq.com/activity/enrollments/open-an-enrollment/): Find one person's enrollment in Activity and read its steps: what has sent, what is scheduled and for when. (markdown: https://support.pynhq.com/activity/enrollments/open-an-enrollment.md) - [Reschedule a campaign step](https://support.pynhq.com/activity/enrollments/reschedule-a-campaign-step/): Move a campaign message to another day by dragging it on the Campaigns calendar, or move the whole campaign by dragging its reference date. (markdown: https://support.pynhq.com/activity/enrollments/reschedule-a-campaign-step.md) - [Review and unpause enrollments](https://support.pynhq.com/activity/enrollments/review-and-unpause-enrollments/): Check the messages of a paused enrollment in Needs Review and release some or all of them, one enrollment at a time or in bulk. (markdown: https://support.pynhq.com/activity/enrollments/review-and-unpause-enrollments.md) - [Stop an enrollment](https://support.pynhq.com/activity/enrollments/stop-an-enrollment/): Cancel everything an enrollment has still to send. Messages already sent stay as they are. (markdown: https://support.pynhq.com/activity/enrollments/stop-an-enrollment.md) - [Enrollment, step and delivery statuses](https://support.pynhq.com/activity/enrollments/reference-enrollment-statuses/): What every status in Activity means, for an enrollment, a step and a delivery, and what moves one to the next. (markdown: https://support.pynhq.com/activity/enrollments/reference-enrollment-statuses.md) - [Messages](https://support.pynhq.com/activity/messages/): Every step Pyn has scheduled or sent, across all enrollments, with its sender, recipients, status and date. Open one to read it as each recipient did. (markdown: https://support.pynhq.com/activity/messages.md) - [Pause a scheduled message](https://support.pynhq.com/activity/messages/pause-a-scheduled-message/): Hold one step of an enrollment so it does not send, and schedule it again when you are ready. (markdown: https://support.pynhq.com/activity/messages/pause-a-scheduled-message.md) - [Read a message as it was sent](https://support.pynhq.com/activity/messages/read-a-message-as-sent/): Open a step in Activity, switch between its recipients to read exactly what each one received, and export the deliveries as CSV. (markdown: https://support.pynhq.com/activity/messages/read-a-message-as-sent.md) - [Resend a bounced message](https://support.pynhq.com/activity/messages/resend-a-bounced-message/): Find out why a delivery bounced, fix the cause, and resend it from the step page or from the bounce notice. (markdown: https://support.pynhq.com/activity/messages/resend-a-bounced-message.md) - [Read the Dashboard](https://support.pynhq.com/activity/read-the-dashboard/): See how many messages Pyn delivered in a period, how many were clicked and how many were actioned, grouped by automation or by step. (markdown: https://support.pynhq.com/activity/read-the-dashboard.md) ## Addons - [Addons](https://support.pynhq.com/addons/): The Addons gallery lists fourteen optional capabilities with what each adds, whether it is Installed, Upgrade Available or Enterprise Tier, and a way to request it. Owners and Admins see it. (markdown: https://support.pynhq.com/addons.md) - [Request an addon](https://support.pynhq.com/addons/request-an-addon/): Ask Pyn for an add-on your workspace does not have by opening its tile in Addons and selecting Upgrade or Request Demo; the tile then shows the request as made. (markdown: https://support.pynhq.com/addons/request-an-addon.md) ## Notices - [Notices](https://support.pynhq.com/notices/): Notices is Pyn's inbox for things that need a person: a bounced delivery, an integration that needs re-authenticating, a webhook that rejected a payload, an export that is ready to download. (markdown: https://support.pynhq.com/notices.md) - [Download an export](https://support.pynhq.com/notices/download-an-export/): Collect a CSV that Pyn built for you from Notices before it expires. (markdown: https://support.pynhq.com/notices/download-an-export.md) - [Read and archive notices](https://support.pynhq.com/notices/read-and-archive-notices/): Work through Open: read what each notice says, open the item it concerns, and archive it once you have dealt with it. (markdown: https://support.pynhq.com/notices/read-and-archive-notices.md) - [Resend bounced deliveries from a notice](https://support.pynhq.com/notices/resend-bounced-deliveries/): Resend every delivery that bounced for a sender in one action, from the bounce notice, once the cause is fixed. (markdown: https://support.pynhq.com/notices/resend-bounced-deliveries.md) - [Choose which notices are emailed](https://support.pynhq.com/notices/set-notice-emails/): Turn on an email to admins when a delivery bounces, when a sender or integration needs re-authenticating, or when a webhook cannot take a payload. (markdown: https://support.pynhq.com/notices/set-notice-emails.md) - [Notice types](https://support.pynhq.com/notices/reference-notice-types/): Every notice Pyn raises: what causes it, who receives it, whether it can be emailed, and what resolves it. (markdown: https://support.pynhq.com/notices/reference-notice-types.md) ## Settings - [Settings](https://support.pynhq.com/settings/): Where admins configure the workspace: the General settings for senders, calendars, users, recipients, webhooks and MCP servers, and the Integrations that connect Pyn to your other systems. (markdown: https://support.pynhq.com/settings.md) - [Account Settings](https://support.pynhq.com/settings/account/): The company name, default time zone and paused state of your workspace, and the Theme page beside it that sets how the emails Pyn sends look. (markdown: https://support.pynhq.com/settings/account.md) - [Pause your workspace](https://support.pynhq.com/settings/account/pause-your-workspace/): Stop Pyn sending messages, running flows and syncing integrations while you make changes, then resume from the same page. (markdown: https://support.pynhq.com/settings/account/pause-your-workspace.md) - [Theme your emails](https://support.pynhq.com/settings/account/theme-your-emails/): Upload a logo and set the colours and font that every email Pyn sends from this workspace uses. (markdown: https://support.pynhq.com/settings/account/theme-your-emails.md) - [Calendars](https://support.pynhq.com/settings/calendars/): Google and Outlook calendars connected to the workspace, which the Invite to calendar event step uses to add employees to recurring events such as orientation or a weekly 1:1. (markdown: https://support.pynhq.com/settings/calendars.md) - [Connect a calendar](https://support.pynhq.com/settings/calendars/connect-a-calendar/): Connect a Google or Outlook calendar, pick which calendar Pyn syncs, and check its events are ready for the Invite to calendar event step. (markdown: https://support.pynhq.com/settings/calendars/connect-a-calendar.md) - [Conditional Senders](https://support.pynhq.com/settings/conditional-senders/): A conditional sender picks a real sender by audience rule, in order, with a fallback, so one step can send from the right regional or departmental identity. (markdown: https://support.pynhq.com/settings/conditional-senders.md) - [Create a conditional sender](https://support.pynhq.com/settings/conditional-senders/create-a-conditional-sender/): Build a sender that routes by audience, for example the UK People team for UK employees and the US team for everyone else. (markdown: https://support.pynhq.com/settings/conditional-senders/create-a-conditional-sender.md) - [Custom Email Recipients](https://support.pynhq.com/settings/custom-email-recipients/): Verified email addresses outside the directory, such as a legal inbox or an agency partner, that a step can send or Cc to. (markdown: https://support.pynhq.com/settings/custom-email-recipients.md) - [Add a custom email recipient](https://support.pynhq.com/settings/custom-email-recipients/add-a-custom-email-recipient/): Add an external or team address, verify it from its inbox, and set the time zone steps should use for it. (markdown: https://support.pynhq.com/settings/custom-email-recipients/add-a-custom-email-recipient.md) - [General](https://support.pynhq.com/settings/general/): The General group in Settings: Needs Attention, Account Settings, Theme, Senders, Conditional Senders, Calendars, Current and Inactive Users, Custom Email Recipients, Webhooks and MCP Servers. (markdown: https://support.pynhq.com/settings/general.md) - [Integrations](https://support.pynhq.com/settings/integrations/): The Integrations group in Settings: the Needs Attention, Installed and Available views, what each tile status means, and the actions every integration panel shares. (markdown: https://support.pynhq.com/settings/integrations.md) - [MCP Servers](https://support.pynhq.com/settings/mcp-servers/): An MCP server exposes chosen workspace operations to AI clients such as Claude or Cursor, limited by a minimum role and by what each connecting person is already allowed to do. (markdown: https://support.pynhq.com/settings/mcp-servers.md) - [Add an MCP server](https://support.pynhq.com/settings/mcp-servers/add-an-mcp-server/): Create a server, choose who may connect and which operations it offers, then share its endpoint with the people who will use it from an AI client. (markdown: https://support.pynhq.com/settings/mcp-servers/add-an-mcp-server.md) - [Set notification emails](https://support.pynhq.com/settings/notifications/): Choose whether Pyn emails you when a delivery bounces, when a sender or integration needs re-authentication, and when a webhook cannot take a payload. (markdown: https://support.pynhq.com/settings/notifications.md) - [Senders](https://support.pynhq.com/settings/senders/): Every identity a message can come from: Google Workspace and Microsoft 365 mailboxes, verified email addresses, Slack users and bots, Teams users and conditional senders, with the statuses the Senders view shows. (markdown: https://support.pynhq.com/settings/senders.md) - [Add a Google or Microsoft 365 sender](https://support.pynhq.com/settings/senders/add-a-google-or-microsoft-365-sender/): Connect a Gmail or Outlook mailbox so messages come from a real person and replies land in their inbox. (markdown: https://support.pynhq.com/settings/senders/add-a-google-or-microsoft-365-sender.md) - [Add a Slack sender](https://support.pynhq.com/settings/senders/add-a-slack-sender/): Connect your own Slack account so direct messages and channel posts come from you rather than the Pyn Bot. (markdown: https://support.pynhq.com/settings/senders/add-a-slack-sender.md) - [Add an email sender](https://support.pynhq.com/settings/senders/add-an-email-sender/): Add a team address such as people@example.com as a sender, verify it from its inbox and send a test. (markdown: https://support.pynhq.com/settings/senders/add-an-email-sender.md) - [Archive a sender](https://support.pynhq.com/settings/senders/archive-a-sender/): Retire a sender you no longer use, after checking which steps still send from it. (markdown: https://support.pynhq.com/settings/senders/archive-a-sender.md) - [Create an auth link](https://support.pynhq.com/settings/senders/create-an-auth-link/): Give an executive or colleague a one-time link that connects their own Google or Slack account as a sender, without a Pyn login. (markdown: https://support.pynhq.com/settings/senders/create-an-auth-link.md) - [Sender types and states](https://support.pynhq.com/settings/senders/sender-types-and-states/): Reference for every kind of sender Pyn supports, how each is added, the medium it serves, and what each status in the Senders view means. (markdown: https://support.pynhq.com/settings/senders/sender-types-and-states.md) - [Users](https://support.pynhq.com/settings/users/): Who can sign in to the workspace and what each role lets them do: Owner, Admin, Power User and User, as shown in the Current Users and Inactive Users views. (markdown: https://support.pynhq.com/settings/users.md) - [Change a user's role](https://support.pynhq.com/settings/users/change-a-users-role/): Promote or restrict a user from the Current Users view by assigning them a different role. (markdown: https://support.pynhq.com/settings/users/change-a-users-role.md) - [Invite a user](https://support.pynhq.com/settings/users/invite-a-user/): Invite a teammate by email, choose their role, and resend the invitation if it does not arrive. (markdown: https://support.pynhq.com/settings/users/invite-a-user.md) - [Remove a user's access](https://support.pynhq.com/settings/users/remove-a-users-access/): Archive a user so they can no longer sign in, and restore them if they return. (markdown: https://support.pynhq.com/settings/users/remove-a-users-access.md) - [Webhooks](https://support.pynhq.com/settings/webhooks/): Inbound webhooks let another system submit a form on an employee's behalf. The Webhooks view lists every webhook with its endpoint, secret state and log. (markdown: https://support.pynhq.com/settings/webhooks.md) - [Create or replace a webhook secret](https://support.pynhq.com/settings/webhooks/create-a-webhook-secret/): Mint the bearer secret a webhook needs before it accepts payloads, copy it once, and rotate it when it is lost or exposed. (markdown: https://support.pynhq.com/settings/webhooks/create-a-webhook-secret.md) ## Integrations - [Integrations](https://support.pynhq.com/integrations/): Connect Pyn to your HRIS, Slack, email, calendars, applicant tracking system and identity provider. One guide per integration, plus references for the fields each HRIS provides and how syncing and matching work. (markdown: https://support.pynhq.com/integrations.md) - [ADP Workforce Now](https://support.pynhq.com/integrations/adp/): Sync employees from ADP Workforce Now with certificate-based API credentials, test the connection, and reconnect when ADP rotates them. (markdown: https://support.pynhq.com/integrations/adp.md) - [Ashby](https://support.pynhq.com/integrations/ashby/): Bring hired Ashby candidates into Pyn as upcoming employees so pre-boarding flows can start before day one. (markdown: https://support.pynhq.com/integrations/ashby.md) - [BambooHR](https://support.pynhq.com/integrations/bamboohr/): Connect BambooHR with your company domain, let Pyn read employees through a BambooHR sign-in, and keep the Directory current with change notifications and a five-minute refresh. (markdown: https://support.pynhq.com/integrations/bamboohr.md) - [Email](https://support.pynhq.com/integrations/email/): The Email integration every workspace has: how Pyn sends email, verified senders, custom domains, bounce handling, and what to tell your IT team to allow. (markdown: https://support.pynhq.com/integrations/email.md) - [Set up a custom domain](https://support.pynhq.com/integrations/email/set-up-a-custom-domain/): Add a sending domain, publish its three DNS records, verify them and make the domain the default for your workspace's email. (markdown: https://support.pynhq.com/integrations/email/set-up-a-custom-domain.md) - [Employee File](https://support.pynhq.com/integrations/employee-file/): Use a spreadsheet as your source of employees: download the sample file, fill the columns, upload it, and re-upload to update. The way to run Pyn without an HRIS. (markdown: https://support.pynhq.com/integrations/employee-file.md) - [Google Workspace](https://support.pynhq.com/integrations/google-workspace/): Send email from Gmail mailboxes and invite employees to Google Calendar events. Each person connects their own account; the integration appears once the first one does. (markdown: https://support.pynhq.com/integrations/google-workspace.md) - [Greenhouse](https://support.pynhq.com/integrations/greenhouse/): Bring hired Greenhouse candidates into Pyn as upcoming employees, using OAuth credentials or, until they retire, a Harvest API key. (markdown: https://support.pynhq.com/integrations/greenhouse.md) - [HiBob](https://support.pynhq.com/integrations/hibob/): Sync employees from Bob by signing in or with a service user, including manager, HRBP, buddy, probation end date and the custom fields you map. (markdown: https://support.pynhq.com/integrations/hibob.md) - [Jira](https://support.pynhq.com/integrations/jira/): Connect a Jira site so an automation can raise a ticket on an employee's behalf, choose which projects steps may use, and reconnect when Atlassian revokes the grant. (markdown: https://support.pynhq.com/integrations/jira.md) - [Microsoft 365](https://support.pynhq.com/integrations/microsoft-365/): Send email from Outlook mailboxes and invite employees to Outlook Calendar events. Each person connects their own Microsoft account. (markdown: https://support.pynhq.com/integrations/microsoft-365.md) - [Microsoft Teams](https://support.pynhq.com/integrations/ms-teams/): Deliver flows as Teams direct messages and channel posts. Teams is in early access: you request it from the Available view and Pyn sets it up with your Teams administrator. (markdown: https://support.pynhq.com/integrations/ms-teams.md) - [Rippling](https://support.pynhq.com/integrations/rippling/): Sync employees from Rippling by signing in or with an API key, choose the related data to expand, and reconnect with a new key when needed. (markdown: https://support.pynhq.com/integrations/rippling.md) - [Sample Data](https://support.pynhq.com/integrations/sample-data/): Install a roster of fictional employees to try Pyn with realistic data, and reload it to put everything back the way it was. (markdown: https://support.pynhq.com/integrations/sample-data.md) - [Slack](https://support.pynhq.com/integrations/slack/): Install Slack so flows can send direct messages, post to channels and invite people to channels, from the Pyn Bot, a custom bot or a colleague's own account. (markdown: https://support.pynhq.com/integrations/slack.md) - [Add a custom bot](https://support.pynhq.com/integrations/slack/add-a-custom-bot/): Create a Slack app from Pyn's manifest so messages come from your own bot name and icon, then paste its bot token into Pyn. (markdown: https://support.pynhq.com/integrations/slack/add-a-custom-bot.md) - [Single sign-on](https://support.pynhq.com/integrations/sso/): Sign your people in through Okta or any OpenID Connect provider, map identity-provider groups to Pyn roles, and understand what employees see at the sign-in page. (markdown: https://support.pynhq.com/integrations/sso.md) - [Connect an OpenID Connect provider](https://support.pynhq.com/integrations/sso/connect-an-oidc-provider/): Connect Keycloak, Microsoft Entra ID, Auth0, Ping Identity or another OpenID Connect provider, set the groups claim, and map groups to Pyn roles. (markdown: https://support.pynhq.com/integrations/sso/connect-an-oidc-provider.md) - [Connect Okta](https://support.pynhq.com/integrations/sso/connect-okta/): Create an OpenID Connect web app in Okta, enter its issuer, client ID and secret in Pyn, and hand out the sign-in link. (markdown: https://support.pynhq.com/integrations/sso/connect-okta.md) - [Workday](https://support.pynhq.com/integrations/workday/): Sync employees from a Workday Report-as-a-Service report: the columns to include, the credentials Pyn needs, and how to read Fields in Report. (markdown: https://support.pynhq.com/integrations/workday.md) - [Fix a sender or integration that needs attention](https://support.pynhq.com/integrations/needs-attention/): Find what has stopped working under Needs Attention, reconnect it, and confirm the status is back to Active. (markdown: https://support.pynhq.com/integrations/needs-attention.md) - [HRIS fields](https://support.pynhq.com/integrations/hris-fields/): Reference for which employee properties each HRIS, ATS and file source provides to Pyn, and where each one comes from in the source system. (markdown: https://support.pynhq.com/integrations/hris-fields.md) - [Sync cadence and matching](https://support.pynhq.com/integrations/sync-and-matching/): How often each integration refreshes, what a refresh does, how records from different sources are matched to one employee, and how a recipient's time zone is decided. (markdown: https://support.pynhq.com/integrations/sync-and-matching.md) ## Account - [Account](https://support.pynhq.com/account/): How you get into Pyn, how you move between workspaces, and what Pyn knows about you as a user. (markdown: https://support.pynhq.com/account.md) - [Profile](https://support.pynhq.com/account/profile/): Where your name, email and photo in Pyn come from, where they appear, and what the profile menu in the corner offers. (markdown: https://support.pynhq.com/account/profile.md) - [Sign in](https://support.pynhq.com/account/sign-in/): The four ways to sign in to Pyn, what happens after you do, and how long a session lasts. (markdown: https://support.pynhq.com/account/sign-in.md) - [Fix a sign-in problem](https://support.pynhq.com/account/sign-in/fix-a-sign-in-problem/): What each message on the Pyn sign-in page means and what to do about it, from an expired magic link to a workspace you cannot see. (markdown: https://support.pynhq.com/account/sign-in/fix-a-sign-in-problem.md) - [Sign in with a magic link](https://support.pynhq.com/account/sign-in/sign-in-with-a-magic-link/): Have Pyn email you a one-time link that signs you in, with no password and no Google or Microsoft account. (markdown: https://support.pynhq.com/account/sign-in/sign-in-with-a-magic-link.md) - [Sign in with Google or Microsoft](https://support.pynhq.com/account/sign-in/sign-in-with-google-or-microsoft/): Use your Google Workspace or Microsoft 365 account to sign in to Pyn without a password. (markdown: https://support.pynhq.com/account/sign-in/sign-in-with-google-or-microsoft.md) - [Sign in with SSO](https://support.pynhq.com/account/sign-in/sign-in-with-sso/): Sign in through your company's Okta or OpenID Connect provider by entering your work email on the Pyn sign-in page. (markdown: https://support.pynhq.com/account/sign-in/sign-in-with-sso.md) - [Sign out](https://support.pynhq.com/account/sign-in/sign-out/): End your Pyn session from the profile menu, or by opening the sign-out address directly. (markdown: https://support.pynhq.com/account/sign-in/sign-out.md) - [Workspaces](https://support.pynhq.com/account/workspaces/): A workspace is one organisation's Pyn. Belong to several, switch between them, and create a new one when you set Pyn up. (markdown: https://support.pynhq.com/account/workspaces.md) - [Create a workspace](https://support.pynhq.com/account/workspaces/create-a-workspace/): Answer four questions about your company, pick up to three priorities, and land in a new Pyn workspace with a setup checklist. (markdown: https://support.pynhq.com/account/workspaces/create-a-workspace.md) - [Switch workspace](https://support.pynhq.com/account/workspaces/switch-workspace/): Move between the Pyn workspaces your email address is linked to, from the profile menu or the Switch Workspace page. (markdown: https://support.pynhq.com/account/workspaces/switch-workspace.md) ## Concepts - [Concepts](https://support.pynhq.com/concepts/): How Pyn fits together, from a workspace and its employees to journeys, flows, steps, deliveries, versions and views, and how the workspace and its data are secured. (markdown: https://support.pynhq.com/concepts.md) - [Data and security](https://support.pynhq.com/concepts/data-and-security/): How a Pyn workspace and its data are protected: sign-in options and SSO, 24-hour sessions and cross-site request protection, roles, owner-only exports, audit log streaming, integration scopes, and what employees are shown. (markdown: https://support.pynhq.com/concepts/data-and-security.md) - [How Pyn fits together](https://support.pynhq.com/concepts/how-pyn-fits-together/): The objects in a Pyn workspace and how one leads to the next: employees from their sources, the journey map, flows and triggers, steps, enrollments and deliveries, published versions, and the views you work in. (markdown: https://support.pynhq.com/concepts/how-pyn-fits-together.md) ## FAQ - [FAQ](https://support.pynhq.com/faq/): Direct answers to the questions Pyn support hears most, from a message that did not send or a channel missing from a list to time zones, HRIS refreshes, Slack permissions and where to report a bug. (markdown: https://support.pynhq.com/faq.md) ## Glossary - [Glossary](https://support.pynhq.com/glossary/): Every term Pyn uses, defined in a line each and linked to the page that explains it, from Account Settings and Audience to Workspace and Version. (markdown: https://support.pynhq.com/glossary.md) ## Changelog - [Changelog](https://support.pynhq.com/changelog/): New features, improvements and fixes in Pyn, one post a week, newest first. (markdown: https://support.pynhq.com/changelog.md) - [Duplicate a step within its flow](https://support.pynhq.com/changelog/week-of-2026-10-19/): Pyn changelog, week of 19 October 2026. A step can now be copied within its flow. (markdown: https://support.pynhq.com/changelog/week-of-2026-10-19.md) - [Escalations, and HR business partners from HiBob](https://support.pynhq.com/changelog/week-of-2026-10-12/): Pyn changelog, week of 12 October 2026. When someone has not completed an action, Pyn can now tell someone else. (markdown: https://support.pynhq.com/changelog/week-of-2026-10-12.md) - [See who has acted in the Actions view](https://support.pynhq.com/changelog/week-of-2026-10-05/): Pyn changelog, week of 5 October 2026. The new Actions view in Activity lists every message that asked an employee to do something: who was asked, what they were asked to do, and whether they clicked or completed it. (markdown: https://support.pynhq.com/changelog/week-of-2026-10-05.md) - [Outlook email and calendars, and Ashby](https://support.pynhq.com/changelog/week-of-2026-09-28/): Pyn changelog, week of 28 September 2026. Pyn now works with Microsoft 365. (markdown: https://support.pynhq.com/changelog/week-of-2026-09-28.md) - [Single sign-on and conditional senders](https://support.pynhq.com/changelog/week-of-2026-09-21/): Pyn changelog, week of 21 September 2026. People can now sign in to Pyn with their work email through your company's single sign-on. (markdown: https://support.pynhq.com/changelog/week-of-2026-09-21.md) - [23 October 2026](https://support.pynhq.com/changelog/2026-10-23/): Covers changes merged from 16 October 2026 at 12:00 am to 23 October 2026 at 8:16 am (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-23.md) - [16 October 2026](https://support.pynhq.com/changelog/2026-10-16/): Covers changes merged from 12 October 2026 at 12:00 am to 16 October 2026 at 7:57 am (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-16.md) - [12 October 2026](https://support.pynhq.com/changelog/2026-10-12/): Covers changes merged from 9 October 2026 at 12:00 am to 12 October 2026 at 8:10 am (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-12.md) - [9 October 2026](https://support.pynhq.com/changelog/2026-10-09/): Covers changes merged from 6 October 2026 at 12:00 am to 9 October 2026 at 8:04 am (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-09.md) - [6 October 2026](https://support.pynhq.com/changelog/2026-10-06/): Period covered: 6 October 2026 at 12:00 am to 6 October 2026 at 6:00 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-06.md) - [4 October 2026](https://support.pynhq.com/changelog/2026-10-04/): Period covered: 3 October 2026 at 12:00 am to 4 October 2026 at 6:06 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-04.md) - [3 October 2026](https://support.pynhq.com/changelog/2026-10-03/): Period covered: 2 October 2026 at 12:00 am to 3 October 2026 at 6:01 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-03.md) - [2 October 2026](https://support.pynhq.com/changelog/2026-10-02/): Period covered: 30 September 2026 at 12:00 am to 2 October 2026 at 7:02 am (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-10-02.md) - [30 September 2026](https://support.pynhq.com/changelog/2026-09-30/): Period covered: 29 September 2026 at 12:00 am to 30 September 2026 at 6:00 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-09-30.md) - [29 September 2026](https://support.pynhq.com/changelog/2026-09-29/): Period covered: 28 September 2026 at 12:00 am to 29 September 2026 at 6:01 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-09-29.md) - [28 September 2026](https://support.pynhq.com/changelog/2026-09-28/): Period covered: 28 September 2026 at 12:00 am to 28 September 2026 at 6:00 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-09-28.md) - [26 September 2026](https://support.pynhq.com/changelog/2026-09-26/): Period covered: 26 September 2026 at 12:00 am to 26 September 2026 at 5:02 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-09-26.md) - [25 September 2026](https://support.pynhq.com/changelog/2026-09-25/): Period covered: 18 September 2026 at 5:01 pm to 25 September 2026 at 5:01 pm (Australia/Sydney). (markdown: https://support.pynhq.com/changelog/2026-09-25.md) ## Site - [For agents and developers](https://support.pynhq.com/for-agents/): Where to find Pyn Help as markdown, JSON and structured data, how the URLs map to pages, and how to cite one. (markdown: https://support.pynhq.com/for-agents.md) ## Optional - [Full content](https://support.pynhq.com/llms-full.txt): every page as markdown, in sidebar order - [Stories index](https://support.pynhq.com/api/stories.json): page metadata and story frontmatter as JSON - [Media index](https://support.pynhq.com/api/media.json): the screenshot and video manifest with absolute URLs - [Sitemap](https://support.pynhq.com/sitemap-index.xml)