- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 06:53 AM
In our organization we are being asked to develop new Help Portals dedicated to specific departments or groups.
Does anyone here have experience with or best practices on taking in these asks?
In your opinion, is it advisable to develop and implement department-specific Portals for logging Incidents, Requests (...), over having a one size fits all Portal?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 11:55 AM
It is not a best practice to create different portals for different groups or departments.
Better create a single portal and define the user criteria on catalog item / KB etc.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 06:13 PM
Hey @Daniel Adriano,
I don't think there is a 'best practice' on whether to have a single or multiple portals. It really depends on the 'why' and what you value the most.
Ask the business why there is a need to design a separate portal for each department.
Once you have that, weigh the value of having multiple portals and the effort/time required to develop and maintain them. Unless there is a critical requirement, most tend to have a single portal.
Hope it helps, cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 11:55 AM
It is not a best practice to create different portals for different groups or departments.
Better create a single portal and define the user criteria on catalog item / KB etc.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 01:50 PM
Based upon these, you can clasiffy the portals
- For all Internal Users (people with snc_internal role)
- External Users (all customers, people with snc_external role)
- For any special customization, intended for specific use
- For IT Security Wing
- For Government Data if any
- For HR
- For DevOps & Operations
- Public Portal open to all users
... continues
🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 06:13 PM
Hey @Daniel Adriano,
I don't think there is a 'best practice' on whether to have a single or multiple portals. It really depends on the 'why' and what you value the most.
Ask the business why there is a need to design a separate portal for each department.
Once you have that, weigh the value of having multiple portals and the effort/time required to develop and maintain them. Unless there is a critical requirement, most tend to have a single portal.
Hope it helps, cheers