Commit 92071ef1 authored by Borivoje Tasovac's avatar Borivoje Tasovac
Browse files

Merge branch 'advocate-onboarding-checklist' into 'master'

Remove duplicate advocates onboarding checklist

See merge request gitlab-com/www-gitlab-com!36816
parents b97b8cd1 1aa1c454
......@@ -42,7 +42,7 @@ _Typically started in first week, completed by end of second week_
 
1. [ ] Check with your manager that you've been given Agent Access to the Community Advocate Zendesk instance.
1. [ ] Quickly check out your Zendesk account to confirm you can login. Explore which platforms are piped into the Zendesk ticket views.
1. [ ] Under your profile on Zendesk, it should read `Agent`. If it reads `Light Agent`, inform your manager.
1. [ ] Under your profile on Zendesk, it should read `Agent` or `Admin`. If it reads `Light Agent`, inform your manager.
1. [ ] Add a [profile picture](https://support.zendesk.com/hc/en-us/articles/203690996-Updating-your-user-profile-and-password#topic_rgk_2z2_kh) to your Zendesk account
1. [ ] [Add Facebook to one of your personal views on Zendesk](https://about.gitlab.com/handbook/marketing/community-relations/community-advocacy/tools/zendesk/#view-limits-workaround).
1. [ ] Open an [Access Request](/handbook/business-ops/it-ops-team/access-requests/)to be added as a ['Light Agent' on the Support Zendesk Instance](https://about.gitlab.com/handbook/support/internal-support/#light-agent-zendesk-accounts-available-for-all-gitlab-staff). Advocates use this instance to check in on support tickets inquired about over Twitter.
......
---
layout: markdown_page
title: Community Advocate Onboarding Checklist
---
This should be located in your general onboarding issue in the [PeopleOps employement issue tracker](https://gitlab.com/gitlab-com/people-ops/employment/issues). This list looks strange in this handbook because it is formatted to be copy-pasted into an issue and then render properly there.
The topics are generally ordered by priority in which they need to be tackled,
but feel free to work on later things in the list when you are waiting on something.
```markdown
1. [ ] Manager: Open a new community advocacy onboarding bootcamp [issue](https://gitlab.com/gitlab-com/marketing/general/issues) using the community advocacy [onboarding checklist](/handbook/marketing/developer-relations/community-advocacy/onboarding/checklist/), and provide the link in a comment below this onboarding checklist.
1. [ ] Shopify
1. [ ] Manager: [Add the new member](https://help.shopify.com/manual/your-account/staff-accounts/create-staff-accounts) as a staff user on our Shopify instance
1. [ ] New team member: Update your [Shopify account](https://help.shopify.com/manual/your-account/staff-accounts/edit-staff-accounts#update-staff-account-details)
1. [ ] Printfection
1. [ ] Manager: [Add the new member](https://help.printfection.com/hc/en-us/articles/114094526173-Managing-Users-in-Printfection) as a user on our Printfection account
1. [ ] New team member: Update your Printfection account
1. [ ] Zendesk
1. [ ] Manager: [Add new team member](https://support.zendesk.com/hc/en-us/articles/203661986-Adding-end-users-agents-and-administrators#topic_h43_2k2_yg) as an agent in [GitLab ZenDesk](https://gitlab.zendesk.com); you may need to [purchase a new license](/handbook/support/workflows/zendesk_admin.html#adding--removing-agents-in-zendesk).
1. [ ] Manager: Add agent to required [support groups](https://support.zendesk.com/hc/en-us/articles/203661766-About-organizations-and-groups) in [GitLab ZenDesk](https://gitlab.zendesk.com).
1. [ ] New team member: Update your [Zendesk account](https://support.zendesk.com/hc/en-us/articles/203690996-Viewing-your-user-profile-in-Zendesk-Support)
1. [ ] New team member: Create a [Hacker News](https://news.ycombinator.com/news) account if you don't have one already, make sure to specify in your user bio that you're a Community Advocate at GitLab, Hacker News requires that we be transparent about any conflicts of interest.
1. [ ] TweetDeck
1. [ ] Manager: Add team member to [TweetDeck](https://tweetdeck.twitter.com/).
1. [ ] New team member: Enable "Confirmation Step" for all GitLab accounts to prevent accidental tweeting.
1. [ ] Disqus
1. [ ] New team member: Create a Disqus account, connect it to your `@gitlab.com` Google account.
1. [ ] Manager: Give the user the ability to moderate Disqus comments on the blog.
1. [ ] Community Forum
1. [ ] New team member: Create new account for the [GitLab community forum](https://forum.gitlab.com/) using the sign in with GitLab option and mention the username used.
1. [ ] Manager: Add new team member to "moderators" group on the [GitLab community forum](https://forum.gitlab.com/).
1. [ ] New team member: Create an account on [Stack Overflow](http://stackoverflow.com/) if you don't already have one.
```
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment