The reader and respond pages

A message is short; the thing it points at can be longer. When the People team attaches an article or a form to a message, the button in the message opens one of two pages in your browser. Neither asks you to sign in or create an account.

The reader page

The reader page shows one piece of content from your company’s Pyn library: a title and the article under it, with the formatting, images and links the author added. It opens from a Link to Library Content button in an email, Slack or Teams message. Opening it records a click on the message; the page itself asks nothing of you.

The address is /reader/ followed by a code. The code identifies the message you received, so the page shows the version of the article that was current when the message was sent, and the link keeps working.

The respond page

The respond page shows a form or poll: its title, each question, and Submit for a form. It opens from a form button in an email. (In Slack the same form appears inside the message instead, with no page to open.)

• Questions can be a checkbox, a five-point scale from Very Dissatisfied to Very Satisfied, a text box, or a block of text to read.
• A required question left blank shows This field is required. when you select Submit.
• A poll records each answer the moment you select it, so it has no Submit button.
• After submitting, the page reads Submitted and Your response has been recorded. Opening the link again shows the same, not the questions.
• Something went wrong with “We couldn’t load this form” means the link is invalid, for example because the message was withdrawn.

The address is /respond/ followed by a code tied to your message, so your answers are recorded against you without a sign-in.

Related

• Acknowledge a message for the buttons that open these pages.
• Answer a form or poll for the steps on the respond page and in Slack.
• Privacy and your data for what the codes in the links carry.