Skip to main content

    Filter by idea status

    Filter by product

    1344 Ideas

    Jared
    JaredInspiring

    Feature Request: Implementation of SAML Role Attribute Mapping for Granular Permissions Management1. New

    Overview:Currently, the SAML SSO connection to your platform provides “all or nothing” access for authenticated users. As any administrator here will know, we need to manually configure the granular roles and permissions within your platform for each new access request, which is time-consuming and introduces potential for error. I am requesting the implementation of SAML Role Attribute Mapping to streamline this process. This enhancement would allow roles or permissions to be dynamically assigned based on attributes sent in the SAML assertion from the identity provider (IdP). Proposed Functionality:• Introduce the capability for the platform to recognize a specific SAML attribute (e.g., Role or Group).• Map the values of the attribute to predefined roles or permission sets within the platform.• Dynamically assign appropriate permissions based on the attribute value, eliminating the need for manual configuration. Benefits:1. Improved Efficiency: Reduces the administrative burden by automating the role assignment process.2. Increased Security: Minimizes the risk of misconfigurations or incorrect permission assignments.3. Scalability: Facilitates onboarding of users with diverse permissions, particularly in organizations with large or dynamic teams. Example Workflow:1. The IdP sends a SAML assertion with an attribute such as Role=ProgramManager.2. The platform maps “ProgramManager” to a predefined role or permission set (e.g., access to Moveworks Setup User, Creator Studio Developer, Creator Studio Analytics Viewer, Creator Studio Logs Viewer, Bot Analytics Admin, Bot Analytics Viewer, Knowledge Studio Viewer, Employee Experience Insights (EXI) Viewer, and Employee Communications User).3. The user gains the appropriate access level automatically upon login. This feature would significantly enhance the usability and security of the SSO integration, aligning with industry best practices for SAML-based access control.  

    ashokmoorthy
    ashokmoorthyInspiring

    Service Now - IRM Approval - Risk Acceptance & Mitigation Approval4. Future Consideration

    Hi Team, Today bot sending few types of native approval notification from Service now - RITM, CHG, Exception Management. We are heavily using both proactive and reactive approval notification mechanism via Red. We are also using SNOW IRM module - Risk & Acceptance Management. We have a custom solution via message API is in place from last one year. We wish to enable this also as part of native approval, so that we can use the same trigger of “show my approval” to show Risk Acceptance and Mitigation approval also via Red.Here is the example of how the message appears today via bot.   I’d like to highlights some recent metrics around this also.How many risk/acceptance requests are submitted every month/quarter/year Overall, 104 risks registered from 01-07-2024 till 31-12-2024. 87 acceptance risk registered. Approx. 15- 20 risks are registered each month, 52 risks are registered every quarter how many approvals needed per request For each risk mandatorily we need 3 approvals and other 2 approvals dependent on risk score. Max is 5 approvals.   how many approvals happening today in every month/quarter/year On an average, 60 to 70 approvals are happening in every month & 156 to 200 approvals are happening every quarter. Who are the audience All are VIPs -  ITLT, SBG LT, VPs and CTOs Once the request/approval submitted, how long does it take to take an action?  Typically approvals are done with in 30 days. But few require more time to get approved. There is a delay due to approvers availability, travelling,..