@@ -83,6 +83,29 @@ We have a limited user seat in 6sense, in order to manage our user seats and pro
During our user audit review, if the user hasn't logged into either the 6sense platform or the dashboards in Sales in the last 6 monmth, their seat willl be revoked.
### 6sense Provisioning to BDR
We only provision 6sense access to BDRs. If AE or SDR request access, please deny and reply with:
>I denied your request for a 6sense license, as we aren't provisioning access to AE, however you can still access 6sense via Salesforce through the account iFrame and 6sense Dashboard in the App Launcher.
When BDRs request for access, we apply, then reply with:
> You need to log into Okta and select the 6sense tile to activate your 6sense user seat which can take up to 24 hours.
>
> Once you've obtain access to 6sense to get start, following the instructions below.
>
> 1. Go to Salesforce
> 2. In the app launcher, search for 6sense Dashboards
> 3. Select 6sense Dashboards - this will take you to the personal dashboard to review 6sense Qualified Accounts (6QA) with high intent
> 4. Add the necessary filters to customize the dashboard by inputting region, employee range, and segments.
> 2. Video tutorials showing how to identify high-intent purchasing accounts3. Best practices for leveraging intent data in your sales approach
Once the BDR activates their 6sense in Okta, they will be added to 6sense with ABM "View Only", you'll need to remove ABM access, and provide SI "SI Lite" Access.
Business Impact Labels: What business impact or subject area is driving these changes
-`MktgImpact - Partner Lead Lifecycle` - Impacts to Vartopia and Partner Lead Lifecycle. Such as the Lead Module, Campaign Module and ROI for channel events and lead tracking.
-`MktgImpact - Partner Lead Lifecycle` - Impacts to Impartner and Partner Lead Lifecycle. Such as the Partner lead, Partner campaign and ROI for channel events and lead tracking.
-`MktgImpact - Sales Enablement` - Marketing initiatives that will help Sales productivity and efficiency
-`MktgImpact - Sales Dev Productivity` - Improves productivity of Sales Dev team, such as SLAs, and visibility
-`MktgImpact - Product Launches` - Issues revolving around a prodct launch or release
@@ -233,38 +233,6 @@ Periodically Marketing Operations and other teams through the marketing org make
## <i class="far fa-handshake" id="biz-tech-icons"></i> Teams We Work Closely With
### Working with Channel Partner Marketing
#### Channel Partner Marketing Expectation
- To open [issues](https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/new) for any new request using the problem statement.
- Channel Partner Team to respond to mktgops queries on the issue
- To provide full problem statement on the issue with as much context as possible.
- Optional - suggested solution for this issue.
#### Marketing Ops Expectation
- To use [labels](/handbook/marketing/marketing-operations/#labeling) to denote where the issue is
- To use [Milestones](/handbook/marketing/marketing-operations/#milestones) to denote when the work will be done
- To provide solution options for the problem statement with clear outline of timeline/ potential blockers.
- To verify possibility of the suggested solution (if there is one).
#### Bi-weekly Meeting
New issues will be prioritized within the bi-weekly meeting where Salina can understand if/what work should be deprioritised to complete the new work.
- Add milestone to the issue of when she thinks the work will be started
If no new issues- can either discuss issues or skip a week.
#### Milestone MRs
The marketing operations team uses collective merge requests, known as our milestone MRs, to make multiple updates across our handbook, see high-level updates in 1 MR, and avoid conflicts with each other. Here is an [example](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/71109). We list all major changes with our GitLab username in the description after a commit and link any relevant issues that the commit closes out. If you have an update for the marketing operations handbook, please feel free to use our milestone MR to make a commit and tag us for review to avoid conflicts.
### Working with Sales Systems for SFDC Updates
The MktgOps team frequently works with the [Sales Systems team](/handbook/sales/field-operations/sales-systems/) to make changes in Salesforce.com (SFDC). See the below information regarding the process for working with Sales Systems for these changes and SLAs we adhere to.
@@ -312,6 +280,10 @@ Workato is a low-code/no-code tool used to for automations and integrations acro
-[How Integrations Team works](/handbook/business-technology/enterprise-applications/integrations/)
### Milestone MRs
The marketing operations team uses collective merge requests, known as our milestone MRs, to make multiple updates across our handbook, see high-level updates in 1 MR, and avoid conflicts with each other. Here is an [example](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/71109). We list all major changes with our GitLab username in the description after a commit and link any relevant issues that the commit closes out. If you have an update for the marketing operations handbook, please feel free to use our milestone MR to make a commit and tag us for review to avoid conflicts.
## Stakeholder Mapping
Stakeholder mapping is a tool to help define roles and to delegate cross-functional responsibilities among the team. Stakeholder mapping connects key functions and jobs across marketing with a primary marketing operations stakeholder, a supporting team of marketing operations team members, and stakeholders outside of marketing operations. The main purpose of stakeholder mapping is to identify and connect the stakeholders involved in setting the strategic direction of marketing operations initiatives.
@@ -379,7 +351,7 @@ Below are tools in the Marketing Technology stack, organized by tier.
@@ -23,82 +23,7 @@ Asana licenses will be rolled out across the entire Marketing Org.
View Only licenses are available to all GitLab team members. If you would like a view only license, please request access in Lumos (please be sure to select View Only permission).
## User Provisioning Guide
### Overview
GitLab team members can request Asana access through the Lumos app store. This guide outlines the provisioning process for Marketing Operations team members.
### Request Flow
1.**Team Member Request**: GitLab team member submits Asana access request via Lumos app store
2.**Manager Approval**: Request is automatically sent to the requester's manager for approval
3.**Marketing Ops Review**: Once approved by manager, request is forwarded to Marketing Operations for provisioning
### Access Entitlements
#### Marketing Team Members
-**Entitled to**: Full Asana license
-**Provisioning method**: Automatic via SCIM (approve in Lumos)
#### Non-Marketing Team Members
-**Entitled to**: View-only access
-**Provisioning method**: Manual invitation through Asana admin console and Lumos
### Provisioning Process
#### Step 1: Verify Team Membership
Check if the requester is on the Marketing team to determine their access entitlement.
#### Step 2A: Full License Request (Marketing Team Member)
If the requester is on the Marketing team and requesting a full license:
1. Approve the request in Lumos
2. User will be automatically provisioned via SCIM
#### Step 2B: Full License Request (Non-Marketing Team Member)
If the requester is NOT on the Marketing team but requested a full license:
1. Comment on the Lumos thread explaining they are only entitled to view-only access
2. Ask the requester to re-submit their request specifically for view-only access
3.**Deny the original Lumos request** (requests cannot be edited)
#### Step 2C: View-Only Request (Any Team Member)
For view-only access requests, manual provisioning is required:
##### Manual Invitation Process
1. Navigate to the [Asana admin console](https://app.asana.com/admin/306855239930259/members)
2. Click **"Invite Members"** in the top right corner
3. In the invitation dialog:
-**Email**: Paste the requester's email address
-**Team**: Select `All Marketing` from the "Add to team" dropdown
-**Projects**: Optionally select specific projects to add them to
-**License**: Select **"View Only"** from the license dropdown
4. Send the invitation
5.**Important**: Click **"Confirm Provisioning"** on the Lumos request
### Key Points to Remember
-**Marketing team members** are entitled to full licenses
-**Non-marketing team members** are entitled to view-only access only
-**Full license requests** from non-marketing members must be denied and re-submitted as view-only requests
-**View-only access** always requires both manual provisioning through the Asana admin console and confirmation in Lumos
-**Always confirm provisioning** in Lumos after completing manual invitations
### Quick Reference
| Requester Team | Request Type | Action |
|----------------|--------------|--------|
| Marketing | Full License | Approve in Lumos (auto-provision via SCIM) |
| Non-Marketing | Full License | Comment, ask to re-submit for view-only, deny request |
| Non-Marketing | View Only | Manual invitation + Confirm in Lumos |
Due to the limited number of full-user seats we have available to us, we will be "pausing" users that have not logged in in over a month. To re-activate, you simply need to login. After you are paused for another month, you will be downgraded to "read only" and will need to request access via Lumos to re-gain your license.
## How to get help with Asana
@@ -316,7 +241,7 @@ If you're unsure which tool to use:
Certain GitLab issues auto-create Asana projects and tasks based on a custom built workflow. More details to be added, but currently only available as a part of the Field Marketing workflow from Allocadia > GitLab > Asana. The majority of tasks and requests should live solely in Asana, please utilize the guide above to know when and how to use GitLab vs Asana.
Details about integration (To be documented)
Details about integration can be found in the [internal handbook](https://internal.gitlab.com/handbook/marketing/marketing-ops-and-analytics/marketing-operations/gitlab-asana-integration/).
### Slack
@@ -380,3 +305,80 @@ Limited integration, but allows you to view live embeds of Figma diagrams and ch
- Click the place in the Brief you'd like to embed.
- Paste in the Figma link and a preview will expand below it.
- You can also click the + icon to the left of the line you're on and choose Insert Media. Paste the Figma link into the box and click Embed link.
## User Provisioning Guide
### Overview
GitLab team members can request Asana access through the Lumos app store. This guide outlines the provisioning process for Marketing Operations team members.
### Request Flow
1.**Team Member Request**: GitLab team member submits Asana access request via Lumos app store
2.**Manager Approval**: Request is automatically sent to the requester's manager for approval
3.**Marketing Ops Review**: Once approved by manager, request is forwarded to Marketing Operations for provisioning
### Access Entitlements
#### Marketing Team Members
-**Entitled to**: Full Asana license
-**Provisioning method**: Automatic via SCIM (approve in Lumos)
#### Non-Marketing Team Members
-**Entitled to**: View-only access
-**Provisioning method**: Manual invitation through Asana admin console and Lumos
### Provisioning Process
#### Step 1: Verify Team Membership
Check if the requester is on the Marketing team to determine their access entitlement.
#### Step 2A: Full License Request (Marketing Team Member)
If the requester is on the Marketing team and requesting a full license:
1. Approve the request in Lumos
2. User will be automatically provisioned via SCIM
#### Step 2B: Full License Request (Non-Marketing Team Member)
If the requester is NOT on the Marketing team but requested a full license:
1. Comment on the Lumos thread explaining they are only entitled to view-only access
2. Ask the requester to re-submit their request specifically for view-only access
3.**Deny the original Lumos request** (requests cannot be edited)
#### Step 2C: View-Only Request (Any Team Member)
For view-only access requests, manual provisioning is required:
##### Manual Invitation Process
1. Navigate to the [Asana admin console](https://app.asana.com/admin/306855239930259/members)
2. Click **"Invite Members"** in the top right corner
3. In the invitation dialog:
-**Email**: Paste the requester's email address
-**Team**: Select `All Marketing` from the "Add to team" dropdown
-**Projects**: Optionally select specific projects to add them to
-**License**: Select **"View Only"** from the license dropdown
4. Send the invitation
5.**Important**: Click **"Confirm Provisioning"** on the Lumos request
### Key Points to Remember
-**Marketing team members** are entitled to full licenses
-**Non-marketing team members** are entitled to view-only access only
-**Full license requests** from non-marketing members must be denied and re-submitted as view-only requests
-**View-only access** always requires both manual provisioning through the Asana admin console and confirmation in Lumos
-**Always confirm provisioning** in Lumos after completing manual invitations
### Quick Reference
| Requester Team | Request Type | Action |
|----------------|--------------|--------|
| Marketing | Full License | Approve in Lumos (auto-provision via SCIM) |
| Non-Marketing | Full License | Comment, ask to re-submit for view-only, deny request |
| Non-Marketing | View Only | Manual invitation + Confirm in Lumos |
