Choose who works on a request
Set the Assignee of a content request, and what only an administrator can change.
What it's for
Each content request can have an Assignee: the team member who looks after it. As a Manager you choose the assignee, change it, or take it off again. Payments, refunds, cancelling and moving the request on stay with an administrator.
Before you start
- You're signed in as a Manager.
- There is a TEST request (fan username starting with TEST) that is not Sent, Declined or Cancelled. Never change the assignee of a real request while testing.
- To check the calendar, assign the test Chatter, not a real person.
Steps
Open the request
Click Operations → Requests, then the All tab (or Needs review). Click the request in the Request column.
Find the Assignee box
Scroll down to the box Assignee. The list Team member shows who is assigned now, or Unassigned.
Choose the person
Open Team member and pick a person. The list has Unassigned and every active person who can send content requests: by default administrators, managers and chatters.
Save it
Click Save assignee.
What you should see
- A message at the bottom right: Assignee saved.
- Assignee at the top of the request shows the name.
- History shows "Assigned to" and the name, for example "Assigned to Jane Example." Choosing Unassigned writes "Unassigned."
- The request shows on that person's Calendar on its due date.
- On a Sent, Declined or Cancelled request, the Assignee box is gone.
What only an administrator can do
On a request, an administrator has an extra box, Update (admin), that you don't have. Only an administrator can:
- move a request to In progress or Ready, and undo Sent (you can mark a request Sent for your own creators: Mark a custom sent),
- cancel a request,
- record what the fan paid (Paid (USD)) and tick Refunded,
- reopen a Declined request,
- remove a file (you can add or replace a file only on requests you sent).
If one of these is needed, ask an administrator.
Test checklist
Good to know
If someone changed the request while you had it open, you see "Someone updated this request. Reload and try again." Reload the page and choose again. If that person lost their access meanwhile, you see Choose an active team member.
You are testing on real data
The test app shares its data with the live app, and a content request can't be deleted. Only work on TEST requests: ones you or the test Chatter sent with a fan username that starts with TEST. Never accept, deny or assign a real request while testing. When you're done, deny the test Chatter's open TEST requests with the note "TEST – done". Ask an administrator to deny or cancel your own.