LogoLogo
👉 Get a free ITSM ebook
Feature Bundle Data Center
Feature Bundle Data Center
  • ➡️About Feature Bundle
    • Key features of Feature Bundle for Jira Service Management
    • Key benefits of using Feature Bundle?
    • 📚 Glossary
    • ITSM vs ITIL
    • ITSM use cases
      • Amazon delivery use case: Improved Jira Ticket Tracking
      • Enriched customer portal: additional values in the incident management process
      • Request types for internal uses
  • Get started - app configuration 🚀
  • Customer Features
    • Access Configuration
      • Customer Portal Access
      • Request Types Access
    • Announcements
    • Request Steps
    • Edit Request
      • Configuration
    • Request View Enhancer
  • Users features
    • Time Tracking for non-agents
  • Admin features
    • Bulk add holidays to SLA calendars
    • Configuration overview
    • Export & Import Request Types
    • Rename SLAs
  • 🤝Support
    • Book a free demo 📆
    • Request a bug 🐞
    • Share your ideas 💡
    • Appsvio website 💻
  • For solution partners
    • Partner Portal
    • Our Partners 🫶
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page

Was this helpful?

Export as PDF
  1. About Feature Bundle
  2. ITSM use cases

Request types for internal uses

With Feature Bundle you can hide request types from customer portal for groups.

Company ABC operates in various regions and provides specialized services tailored to each region's requirements. To manage service requests effectively, Company ABC has configured organization-specific request types in their Jira Service Desk portal. However, certain request types are relevant only to employees within specific organizations and should not be visible to customers from other organizations.

  1. Configuration of Organization-Specific Request Types:

    • The IT administrator, John, configures organization-specific request types in the Jira Service Desk portal to streamline service request management for employees across different regions.

    • Each organization is assigned specific request types tailored to their needs, such as IT support, facilities maintenance, and HR inquiries.

  2. Identification of Request Types that should be restricted from Customers:

    • John identifies certain request types that are relevant only to employees within specific organizations and should not be visible to customers from other organizations.

    • For example, a request type related to regional office infrastructure maintenance is specific to employees within the respective regional organization and should not be visible to employees from other regions or external customers.

  3. Configuration of Visibility Conditions:

    • John configures visibility conditions for the organization-specific request types to ensure that they are only visible to employees within the respective organizations.

    • He defines conditions based on organization membership, ensuring that only employees associated with the relevant organization can view and access the specific request types.

  4. Testing and Validation:

    • John conducts thorough testing to ensure that the visibility conditions are properly configured and functioning as intended.

    • He validates the configuration by logging in as users from different organizations and verifying that they can only view request types relevant to their organization.

  5. Implementation and Communication:

    • Once validated, John implements the visibility conditions for the organization-specific request types in the live Jira Service Desk portal.

    • He communicates the changes to all employees, informing them that certain request types are tailored to their organization's needs and may not be visible to users from other organizations.

  6. Monitoring and Maintenance:

    • John monitors the portal regularly to ensure that the visibility conditions remain effective and that only authorized users can access organization-specific request types.

    • He addresses any issues or discrepancies promptly and makes necessary adjustments to the visibility conditions as organizational requirements evolve.

By configuring visibility conditions based on organization membership, Company ABC ensures that employees have access to request types relevant to their organization's needs while maintaining confidentiality and preventing unauthorized access from external customers. This approach enhances service request management and ensures a tailored service experience for employees across different regions.

PreviousEnriched customer portal: additional values in the incident management processNextGet started - app configuration 🚀

Last updated 11 months ago

Was this helpful?

➡️