Choose access around the person’s next action. A Request response link and a channel invitation solve different needs.

Before you start

Decide whether the person needs to answer a specific prompt, return regularly to create, or distribute existing assets.

Steps

  1. Step 1. For one contribution, create a Request with a clear question and required response type. Finish its setup and activate/share it; a saved draft is not ready to collect answers.

  2. Step 2. Copy the active Request link and open it to check the questions, terms and response experience. Send that link with the deadline and expected answer length.

  3. Step 3. For recurring creation, use Invite Users → Standard & other roles. Assign the available Contributor/VIP Guest or Member role that fits their work, then send the invitation.

  4. Step 4. For distribution, use Invite Users → Social user. Invite by email, then point the person to an approved asset in the channel.

  5. Step 5. Verify the correct outcome: a submitted Request response, an accepted channel invitation plus a first contribution, or a completed sharing task.

Check the result

The person has a clear task and suitable access. Answering a Request does not automatically make someone a channel administrator or give access to the media library.

If something does not work

  • An inactive Request link: check draft, paused or closed status before reinviting the person.

  • A Social user needs to record or edit: ask an Admin to reassess the role; sending the same content link will not unlock creation.

  • A guest cannot see a private group: check group membership separately from channel membership.

Related: Build and share Requests · Send channel invitations · Social user walkthrough


Keep exploring