By Jeanb-Oracle on Dec 08, 2014
If you are an administrator for your organization's Oracle software and systems, you may have been tasked with managing your employees' access to My Oracle Support, the central support hub for all of your Oracle products. Each user that accesses My Oracle Support has an assigned Support Identifier (SI) that links him or her to a particular piece of Oracle hardware or software. Support Identifiers define the resources available to users when they access My Oracle Support.
However, suppose your My Oracle Support users are scattered across a broad geographic area, or you have numerous Support Identifiers referencing dozens (or possibly hundreds) of software and hardware assets. Mapping users to the correct Support Identifier can become time consuming, especially if you need to align privileges and service request flows to specific projects, locations, or assets.
Support Identifier Groups (SIGs) simplify this process by allowing Customer User Administrators (CUAs) to group common SIs together. This makes it dramatically easier to group users at a common location, or who work on a common software or hardware asset.
To use the new Support Identifier Groups, you will need to pre-plan how users and assets are best organized. Once defined you can set up SI Groups in My Oracle Support, adding users and assets logically the way you need them.
Simple. Easy. Maintainable.
When your organization adds new hardware or software (with an associated new SI), you can automatically re-assign them to a designated default group. New assets added to a default SI Group are immediately available to the group's associated users; you do not have to setup or re-approve users you have already assigned.
Learn more about SI Groups and how they can help you.