Skip to content
English
Contact
  • There are no suggestions because the search field is empty.

Configuring Stackgini Catalog

The flexible Catalog configuration connects users with your internal software portfolio, enabling seamless discovery and access requests and new IT requests directly within your existing IT workflows.

Contents

  1. Configuring Software Access Request Routes

    1. Configuring access request routes for suggested software
    2. Configuring new software request routes

  2. Embedding Catalog in Third-Party Platforms

    1. Prerequisites for Embedding Catalog
    2. Example: ServiceNow implementation guide 
    3. Embedding Catalog in other platforms

1. Configuring Software Access Request Routes

With Stackgini Catalog configuration you can:

  • Configure global and application-specific access request routes
  • Direct new software requests to your intake processes
  • Embed Catalog in third-party platforms like ServiceNow, Freshservice, SharePoint, Confluence via iframe
  • Maintain user authentication and authorization through SSO
  • Import application access request routes via CSV or API during portfolio setup

To access Catalog settings, go to Organization Settings > General and you'll find configuration options for request routes and embedding parameters.

a. Configuring Access Request Routes for Suggested Software 

Overview

Access request routes direct users to the appropriate workflow when they select software from Stackgini Catalog. When no access request route is configured, the access request button will not display in the Catalog.

Stackgini supports a two-level routing hierarchy:

  1. Global default route: Applies to all software in Catalog unless overridden
  2. Application-specific routes: Individual routes configured per sitem in your portfolio

This allows flexibility: use a global route for standard requests, then override specific applications with custom workflows.

Set up the global default access request route

The global default route applies to all software in your Catalog unless individual applications have their own custom routes configured.

To configure the global default route:

  1. Go to Organization Settings > General
  2. In the Catalog section and URL or email to request access section, choose your route type:
    • URL: For routing to a web-based request system
    • Email: For routing requests to an intake mailbox
  3. Enter the URL or email address
  4. Save your changes

Important: If you do not configure this section, the access request button will not appear for any software in your Catalog.

URL routing with dynamic software name

When using a URL route, include a{name} parameter which will be replaced with the URI-encoded application name. Example: For Jira to fill the Jira Summary field with the applicatio name.

https://your-domain.atlassian.net/servicedesk/customer/portal/1/create/3?summary=Request%20access%20to%20{name}

When a user selects "Microsoft Teams," the URL becomes:

https://your-domain.atlassian.net/servicedesk/customer/portal/1/create/3?summary=Request%20access%20to%Microsoft%20Teams

Example configurations:

  • ServiceNow: https://your-domain.service-now.com/now/nav/ui/classic/params/target/com.glideapp.servicecatalog_category_view.do%3Fv%3D1%26sysparm_parent%3D2809952237b1300054b6a3549dbe5dd4%26sysparm_catalog%3De0d08b13c3330100c8b837659bba8fb4%26sysparm_catalog_view%3Dcatalog_default%26sysparm_view%3Dcatalog_default
  • Jira: https://your-domain.atlassian.net/servicedesk/customer/portal/1/create/3?summary=Request%20access%20to%20{name}

Setting application-specific access request routes

You can configure different access request routes for individual applications in your portfolio. Application-specific routes override the global default route for that application item.

To configure an application-specific route:

In your portfolio, open the application details and add an License Request field entry. This route will be used instead of the global default when users request access to this specific application.

Import via CSV or API:

Application-specific routes can be bulk-imported when populating your portfolio:

  • CSV import: Include an license_request column with URL or email values for each application
  • API import: Pass the "licenseRequest" parameter when creating or updating application records (Also see documentation here: Swagger UI )

b. Configuring New Software Request Routes

Set up request route for new software initiatives

When users cannot find suitable software in Catalog, they need a way to propose new software for your organization. This route directs them to your new software request intake process.

To configure the new software request route:

  1. Go to Organization Settings > General
  2. Navigate to Catalog section
  3. In the URL to create software request section, enter your target URL
  4. Leave blank to use Stackgini's built-in software request form (recommended for new implementations)
  5. Save your changes

When to configure a custom URL:

  • Your organization has a dedicated software request approval workflow
  • You are routing new software requests through an existing IT service management system

Example configurations:

  • ServiceNow: https://your-domain.service-now.com/now/nav/ui/classic/params/target/dmn_demand.do
  • Jira: https://your-domain.atlassian.net/servicedesk/customer/portal/1/group/4/create/109

Default behavior: Initiative creation assistant

When no custom URL is configured in the URL to create software request field, the system uses Stackgini's built-in Initiative Creation Assistant by default. This is the recommended approach for most organizations.

 

2. Embedding Catalog in Third-Party Platforms

Embedding Stackgini Catalog in third-party platforms brings your internal software marketplace directly into users' existing workflows. Instead of requiring users to navigate to a separate portal, embedded Catalog integration allows them to discover software and request access from within ServiceNow, SharePoint, Freshservice, Confluence, or any platform that supports iframe embedding.

Key benefits of embedding:

  • Users access software discovery within their daily tools and workflows
  • Seamless single sign-on (SSO) authentication ensures frictionless access
  • Let users request new software in free-text even if they do not already know which software they are looking for but maybe only have a problem they want to solve with a software
  • Drive re-use of existing systems with our intelligent catalog agent which also can recommend alternatives from your internal software inventory when users request tools from the market which you do not have

How it works:

Embedding uses standard HTML iframes to display the Stackgini Catalog interface within another platform. The iframe code is identical across all platforms. Your platform domain is registered in Stackgini's security allowlist, and SSO ensures that users are authenticated using their existing organizational credentials.

The following sections cover prerequisites, supported platforms, and detailed implementation guides for ServiceNow and other platforms.

a. Prerequisites for Embedding Catalog

Before embedding Stackgini Catalog in any third-party platform, ensure the following prerequisites are met.

Single Sign-On (SSO) configuration

Stackgini must be configured with your organization's SSO provider (Azure AD, etc.). This ensures seamless authentication when users access the embedded catalog without requiring separate credentials. When SSO is properly configured, users are automatically authenticated based on their existing session, providing a frictionless experience.

User access and Azure group provisioning

All users who will access the embedded catalog must be:

  • Added to the relevant Stackgini user groups in your AD groups
  • Members of appropriate Azure AD groups (if using Azure AD)
  • Provisioned in both Stackgini and the third-party platform where the catalog is embedded (Happens automatically for Stackgini if the user is in the appropriate Azure AD group providing access to Stackgini)

For detailed guidance on user provisioning and Azure AD group configuration, refer to the following aticle: Single-Sign-On (SSO) Setup Via Azure AD / ENTRA ID 

Supported platforms

Stackgini Catalog can be embedded in any platform that supports custom iframe embedding. This includes for example:

  • ServiceNow (documented in detail below)
  • Microsoft SharePoint
  • Atlassian Confluence
  • Freshservice
  • Any other platform supporting iframe embedding

Important: The Stackgini Catalog embedding code uses a standard HTML iframe that works across all platforms. The only requirement is that your platform supports embedding custom HTML or iframes. Configuration steps may vary slightly depending on your platform's widget framework, but the underlying iframe code remains the same.

b. Example: ServiceNow implementation guide

This section provides step-by-step instructions for embedding Stackgini Catalog in ServiceNow.

Step 1: Identify the target page in your Service Portal

Before configuring the widget, determine where in your Service Portal you want to display the Catalog. Consider these options:

  • Create a new page dedicated to "Software Catalog" 
  • Embed on an existing "IT Services" or "Software Request" page
  • Add to the Service Portal homepage with clear Call-to-Action e.g. Search or Request Software - Browse the software catalog for items your need (Recommended)

Step 2: Create a custom Stackgini Catalog widget

  1. Log in to ServiceNow as an administrator
  2. Go to Filter Navigator (search field at the top of ServiceNow) and search for Service Portal > Widgets
  3. Click New in the list view to create a new widget
  4. Enter the widget details:
    • Name: Stackgini Catalog
    • ID: stackgini_catalog
    • Description: Embedded Stackgini software catalog for requesting access

Step 3: Add the HTML Template code

In the HTML Template tab, replace the default content with the following iframe code, which you can copy from Stackgini under Organization Settings > General:

iframe code exmaple (Will be different for you tenant)

<div class="iframe-container" style="width:100%; height:100vh;">   <iframe     src="https://app.softwaregini.com/your-tenant/embed/catalog"     style="width: 100%; height: 100%; min-width: 768px; border: none;"     allow="clipboard-write"   ></iframe> </div>

The iframe code explanation:

  • class="iframe-container": Container div with full width and viewport height
  • src="https://app.softwaregini.com/your-tenant/embed/catalog": Your Stackgini embed URL (your tenant URL will be pre-configured)
  • style="width: 100%; height: 100vh...": Makes the iframe responsive and full-screen
  • min-width: 768px: Ensures minimum width for optimal rendering
  • allow="clipboard-write": Enables clipboard functionality for copy features

Step 4: Add the Client Script

In the Client Script tab, add the following controller code:

javascript

api.controller = function() {   /* widget controller */   var c = this; };

This minimal controller initializes the widget. You can extend this for future enhancements like custom analytics or event tracking.

Step 5: Add the Server Script

In the Server Script tab, add the following code:

javascript

(function() {   /* populate the 'data' object */   /* e.g., data.table = $sp.getValue('table'); */ })();

This handler is available for future customization, such as:

  • Logging requests for audit purposes
  • Pre-populating user information from ServiceNow

Step 6: Configure CSS and access control

In the CSS tab, you can leave it empty (recommended) or add custom styling.

Step 7: Add widget to your Service Portal page

  1. Go to Filter Navigator and search for Service Portal > Configuration
  2. Click Designer
  3. Open your target Service Portal and select or create the page where you want to embed Catalog
  4. In the Service Portal Designer, the left sidebar displays available widgets and layout tools
  5. Search for Stackgini Catalog in the widget list
  6. Drag and drop the Stackgini Catalog widget onto the canvas to your desired location
  7. Click on the widget to adjust sizing and positioning as needed
  8. Click Save in the top right corner to save your changes to the page
  9. Publish or deploy the page to make it live to users

Step 8: Register your ServiceNow domain in Stackgini

To allow your ServiceNow instance to embed Catalog, you must register it in Stackgini:

  1. Log in to your Stackgini tenant
  2. Go to Organization Settings > General
  3. Navigate to Catalog section
  4. In the Allowed iframe domains section, add your ServiceNow domain (one per line):
https://your-instance.service-now.com

Save changes (may take up to 5 minutes to take effect).

Step 9: Test the integration

  1. Access your Service Portal as a regular user
  2. Navigate to the page with the embedded Catalog
  3. Verify the following:
    • Stackgini Catalog loads without errors
    • SSO authentication passes through correctly
    • Clicking software items opens the configured access request route

c. Embedding Catalog in other platforms

The Stackgini Catalog embedding code is platform-agnostic and works in any platform that supports custom iframe embedding. The HTML iframe code remains identical across all platforms; only the configuration steps differ based on each platform's framework.

SharePoint embedding

Use the HTML Web Part (or Embed web part) to add the iframe code to your SharePoint page:

  1. Edit your SharePoint page
  2. Add an "HTML Web Part" or "Embed" widget
  3. Paste the iframe code into the HTML editor
  4. Ensure your SharePoint domain is added to Allowed iframe domains in Organization Settings > General (Catalog Section)

Confluence embedding

Use the HTML macro to embed the iframe in your Confluence page:

  1. Edit your Confluence page
  2. Insert the HTML macro (or HTML Include macro depending on your version)
  3. Paste the iframe code into the macro
  4. Ensure your Confluence domain is added to Allowed iframe domains in Organization Settings > General (Catalog Section)

Freshservice embedding

Freshservice supports embedding external content in its IT Service Management portal through custom sections and widgets. You can add Stackgini Catalog to your Freshservice instance using custom sections with iframe support:

  1. Log in to your Freshservice instance as an administrator
  2. Go to Admin > Account Settings > Service Desk Rebranding > Customize support portal
  3. If your account has multiple workspaces, navigate to Admin > Global Settings > Account Settings > Service Desk Rebranding > Customize support portal
  4. Click on the home page or target page card to access the editor
  5. In the page designer, add a custom section by hovering between existing sections and clicking the + button
  6. Select a section layout (1-4 columns based on your needs)
  7. In your section, add a Text widget or create a custom HTML section
  8. Copy & Paste the iframe code into the HTML editor which you get from Stackgini Organization Settings > General (Catalog Section)
  9. Save your changes to the page layout
  10. Ensure your Freshservice domain is added to Allowed iframe domains in Organization Settings > General (Catalog Section)
  11. Test with sample users to verify SSO authentication and Catalog functionality

Note: Freshservice requires that embedded content comes from the same domain or has proper cross-origin resource sharing (CORS) headers configured. If users see blocked content warnings, work with Freshservice support to ensure Stackgini's domain is allowlisted in your Freshservice security policies.

Custom intranet portals

For custom-built portals or other platforms:

  1. Locate the page template or HTML editor where you want to embed Catalog
  2. Paste the iframe code directly into your page's HTML
  3. Add your portal domain to Allowed iframe domains in Organization Settings > General (Catalog Section)
  4. Test with sample users to verify SSO authentication and functionality

General embedding guidelines

For any platform:

  • The iframe code is the same across all platforms
  • SSO must be configured for seamless authentication
  • Your platform domain must be added to Allowed iframe domains in Stackgini
  • Content Security Policy (CSP) headers may need adjustment for some platforms
  • Minimum iframe height is typically 600px; full viewport height (100vh) is recommended