Partner Management

FAQs

Where can the partner users be invited in SAMi?

[Ans]: Under current Manage tab in Apps page/ teams & home page.

2. When is partner support needed?

[Ans]: Partner support will be needed only if license issued to customer has Partner Support feature enabled.Modified requirement - to accomodate this item.

3. Are there new Roles needed?

[Ans]: New roles - Partner publisher and Partner Subscriber are neededRoles added under: https://sidgs.atlassian.net/wiki/spaces/SAMI2/pages/2674196540

4. Is partner Subscriber the same as subscriber?

[Ans]: Yes, but we need a way to distinguish between partner subscribers & non-partner onboarded users. There can be a case where a user can fit into both Subscriber & Non-partner-Subscriber roles and that is fine as long as the apps, teams & accounting lines are separate - differentiation between initiation/action of/on journeys through partner or self.

5. Is a Partner Publisher same as the Publisher?

[Ans]: No -

1. A partner publisher cannot create, update or delete product categories, but can view assets in his/her role.

2. Resell products published by the publisher [Bulk SKUs or product bundles use case]

3. Partner Publisher cannot approve on any requests.

6. How is a partner recognized?

[Ans]: [Proposed] A partner is identified by a partnerID/Name which will be associated with a partner company name or even as simple as a team.

7. What is the relationship between a partner publisher & Publisher?

[Ans]: 1 Publisher can onboard 1 or more partner publishers inclusive of approvals to onboard users to the partner owned team.

8. What is the relationship between a partner publisher & partner subscriber?

[Ans]: 1 partner Publisher can onboard 1 or more partner subscribers with approvals from publisher or partner publisher.

9. What is the relationship between a publisher & partner subscriber?

[Ans]: Publisher cannot onboard 1 or more partner subscribers.

10. Does the org admin play a part in this whole scenario?

[Ans]: Ideally no, but an admin can play the role of a publisher if there is a need or a customer ask to restrict the number of roles or rename roles as part of customization.

11. Why "Partner Publishers" invites the "Partner Subscribers"? (Do you mean Partner Subscribers are their internal users?)

[Ans]: Partner Publishers will have a business need to 1. create their own products & apps or 2. resell existing products of publisher. In order to create their own products and apps, Partner Publishers need developers to realize the apps. Any ‘Partner' user is external to SAMi’s scope, not internal. Having said that, it is not in SAMi’s interest to track if Partner Subscribers are internal users of the partner publisher or contracted or any other model.

12. The Products onboarded by partner publisher will be visible to public or it will only be visible to their invited partner subscribers?

[Ans]: Products onboarded by partner publisher if permissioned for Guest will be made public. Any invited subscribers must also be able to view when invited or if they chance upon them publicly.

13. How to handle partner publisher product Management? How partner publisher will add others to manage his/her product.

[Ans]: Same way how the current Publisher manages. Q5 answers the above8. How partner publisher will request.

14. Publisher to sell his products especially mutliple or bundle of products?

[Ans]: Partner Publishers will not request a Publisher to sell their products. Reselling scenario is - publisher's products are resold by partner publisher.

15. How partner publisher will resell the products that he purchased from the publisher?

[Ans] Partner Publisher place an order for X-quantity of 1 or more products. Publisher has to grant X-quantity SKUs to partner publisher. Now its partner publisher's responsibility to resell the SKUs to subscribers.

16. We are not creating new roles to differentiate Publisher and Partner Publisher. If the user has (Publisher, Internal ) role then he/her is Publisher and User with only (Publisher) role is Partner/External publisher.

[Ans]: First part of the above query needs design considerations. In the second part, how do we distinguish between a publisher and a Partner Publisher? So its better we do it with roles. Introducing a flag - 'IsPartner' user is a quick hack at the user level. From a development perspective we need to evaluate which of the above option is better in terms of a new role or using a new flag for each user [no role changes here].

17. Why "Partner Publisher" will invite other "Partner Publisher"?. How and why he will control my portal?

[Ans]: 1. To increase scope of business, as a partner is expected to bring in more business which the publisher cannot invest his time into. The permissions for a partner publisher is not to administer the portal, but will have all capabilities of a publisher [here the similarities end], but will be an external user. A publisher would be able to request for new category for products which we should set in the roles and hence my recommendation is to use role-based differentiation rather than a flag-based differentiation. Due to above permissioning, Partner subscriber's roles will also need to have a new role as Partner Subscriber whose differentiation would be - invited by a Partner Publisher or another Partner Subscriber, external users but role capabilities same as a subscriber.