Identifying users for Business Stakeholder Licences
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Hi
I want to identify users that are currently consuming Fulfiller licences that could be candidates for Business Stakeholder licences.
Can anyone suggest a method I could use?
The technical way I can think of is to query the sys_audit or sys_history table and identify when each user last created, modified or deleted a record or report. I'm told this would be a big query though. Could presumably just identify who has made updates in last 3 or six months and then fulfiller user not in the list hasn't made an update.
Any thoughts on how I can do this?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
That will not give you a good overview. It's more about 'who should be able to do what'.
Check on the groups you are using. And send the managers of those groups an overview of the members and ask them what these people should be able to do and why. The system is only going to tell you what someone did, not what they should do.
It could very well turn out that someone is still member of the ServiceDesk group, while they are already promoted to management, but still use the backend to create their tickets instead of the portal, just because they can.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Thanks Mark, however at the moment I'm more concerned about identifying people who can but don't. Whether or not they should is a question for another day.
My conversation is easier if I can contact specific managers about specific staff who are not using their license and do that on a regular basis, or have a rule that people who don't use it, lose it or get migrated to business stakeholder. Polling all managers, where I have over 2500 users is not practical or effective