Label Insight - SmartLabel Team and Permissions

Modified on Thu, 21 Sep, 2023 at 9:56 AM

Label Insight requests that you submit a contact list of the users that will be interacting in our platform. Below is the list of roles we typically see involved from previous customers. If there are roles in here that fall outside your agreed upon workflow, you can simply skip those. You can submit this via the help widget in the platform. 


SmartLabel Program Lead - the main point of contact for the implementation.


Business Sponsor - an individual from the executive team who is the sponsor for the SmartLabel implementation.


Brand Manager(s)/ Marketing - team member(s) knowledgeable in, and responsible for, brand packaging, off-package information, production deadlines (on shelf), marketing of responsible product(s), brand messaging/voice, etc.


Legal - team member(s) responsible for reviewing information such as GMO disclosure, ingredient descriptions, and off-package claims.


Regulatory - team member(s) concerned with GMO disclosure, ingredient descriptions, off-package information, and general compliance with government regulations and risk.


IT - team member(s) responsible for any electronic information exchange (ex: via API), as well as platform access, URL usage for brand.com sites, security, etc.

Next will be determining what permissions these users should have. Our platform has three options: View, Edit, and Publish. 


View - User can see all products within a given Org


Edit - User can see and edit all products with a give Org


Publish - User can see, edit and publish products within a given Org


When submitting the contact list, please include in an Excel sheet the persons first and last name, email address, and permissions you'd like them to have in a Zendesk ticket. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article