Clarification on Licensing Impact for Custom Role with Read Access on Project Table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi everyone,
I have a requirement to show projects on the portal for users listed in the Additional Assignee List (treated as stakeholders), so that they can view project details and add comments.
As I want to avoid assigning the it_project_manager role due to licensing concerns, I am planning the following approach:
- Create a Record Producer on the portal
- Display a list of projects associated with the stakeholder
- Allow users to select a project and submit comments
- Update the comments on the project via Flow or field mapping (e.g., Additional Comments field)
To support this, I am considering creating a custom role with read ACL access on the pm_project table, without providing direct write/update access.
Clarification Required:
Will this approach be considered non-licensable, since users will only have read access and interact via the portal? Or could ServiceNow treat this as licensable usage, even with a custom role and limited access?
> > From my understanding, licensing depends more on user activity (e.g., updating or managing records) rather than just the role itself....
Thanks,
Kaushal
