My Kentik Portal

The following topics cover the configuration, in the Kentik portal, of My Kentik Portal (MKP), which is Kentik's implementation of tenancy:

• About Tenancy
• My Kentik Portal Page
• Tenants Tab
• Packages Tab
• MKP Settings Page
• Tenant Settings Pages
• Package Settings Pages
• Configuring Tenancy

Note: For information on the MKP portal that is seem by your tenant users, see MKP Tenant Portal.

General information about tenancy and the My Kentik Portal is covered in the following topics:

• Tenancy Overview
• Tenancy Structure
• Tenancy Use Cases
• Enabling Tenancy
• Tenants and Packages

The My Kentik Portal enables Kentik to support tenancy. Tenancy is a mechanism by which a Kentik customer can make available to its own external or internal customers (the “tenants”) a limited, customer-branded version of the Kentik portal. Customers assign users to a given tenant, which enables those users to see a curated set of visualizations and metrics that are filtered to show only their own traffic.

Note: As used in the context of tenancy, the term “user” does not refer to a registered Kentik user, but rather to a user that a Kentik customer assigns to one of its tenants.

Kentik's implementation of tenancy is structured as follows:

• My Kentik Portal: Each Kentik customer may stand up a single tenant portal, called the My Kentik Portal:
  - The Kentik customer is effectively the "landlord" for their tenants.
  - The tenant portal is a much-simplified version of the Kentik portal. It includes a Library (for Dashboards and Saved Views), a Traffic Explorer (simplified version of the Kentik portal's Network Explorer), and some information related to alerting and mitigation. For more information, see MKP Tenant Portal.
  - The URL is the same for all of your tenants.
  - It’s branded with your logo, and may optionally include your support information.
• Tenants: Each Kentik customer has a set of tenants:
  - If you’re a provider, each tenant typically corresponds to one of your subscribers.
  - The maximum number of tenants per customer depends on your Kentik edition (see Kentik Editions).
  - The types of reports available to a given tenant, and the characteristics (e.g. devices, CIDRs, etc.) of the shown traffic, are specified with the settings on the Tenant Settings Pages.
  - Common settings for multiple tenants may be implemented with "packages" (see Packages Tab).
• Users: Each tenant may have an unlimited number of users, each of which is assigned to it by the landlord via the Tenant User Settings.

Tenancy is designed for two main use cases:

• The Kentik customer is a service provider and the tenants each represent a customer of the provider, each of which has any number of individual users who can access the tenant portal.
• The Kentik customer is an enterprise and each tenant is a different group within the company, each of which may have very different needs in terms of the network traffic data they need to see and the form in which the data should be presented. The views available to a given user in the tenant portal differ depending on the tenant to which the user has been assigned.

The tenancy feature is enabled by default, but the number of tenants supported by your Kentik subscription is determined by your organization's edition of Kentik (see About Licenses). To obtain unlimited tenant support, you can purchase Kentik's Advanced MKP option. For details, please contact Customer Support.

The configuration of MKP tenancy in the Kentik Portal (on the My Kentik Portal Page reached from the main navbar) is structured into two parts:

• Tenants: Each tenant is an external or internal entity to whom you, as a Kentik customer, make available a self-branded version of the Kentik portal so that the tenant's users can access a limited subset of Kentik-derived information about your network's status and performance.
• Packages: Each package is effectively a collection made up of the following:
  - Views: One or more individual views (charts, tables, etc.) that provide the tenant's users with information about the network. The MKP seen by your tenant's users will be a dashboard containing these views.
  - Alert policies: A set of alert policies that trigger alarms (notifications) to your tenant's users when a set of custom-defined conditions are met.

Using a package enables you to assign a collection of views and policies as a group, so that you can assign the same collection to multiple tenants rather than having to repeatedly assign the individual items in the collection.

The following general guidelines apply to the relationship between tenants and packages:

• When a package is assigned to a given tenant all of that tenant's users see all of the views (and get the alarms) associated with that package.
• Each tenant can currently be assigned only one package at a time.
• A given tenant may also be assigned as many individual views as you (the Kentik customer) choose to assign them.

The My Kentik Portal page is home to the settings needed to configure and manage tenancy. To view the page, choose My Kentik Portal from the main Kentik portal navbar.

The My Kentik Portal page has the following main UI elements:

• Settings: A button that takes you to the MKP Settings Page.
• Tenants tab: Home of the Tenants List and other controls and indicators used to configure and manage the tenants who use your organization's My Kentik Portal (see Tenants Tab).
• Packages tab: Home of the Packages List and other controls and indicators used to configure and manage the views and alert policies that can be assigned to your organization's MKP tenants (see Packages Tab).

The Tenants tab of the My Kentik Portal page, used to create and manage tenants (see Tenancy Structure), is covered in the following topics:

• Tenants Tab UI
• Tenants List

The Tenants tab contains the following main UI elements:

• Filter field: Filters the Tenants List to show only the tenants whose name contains the entered text.
• Add Tenant: A button that opens the Add Tenant page (see Tenant Settings Pages).
• Tenants List: A list of the tenants currently set up in your organization (see Tenants List).
• Tenant Overview: An information pane at the right of the page that shows how many tenants are allowed under your organization's edition of Kentik (see About Licenses) and how many of those are currently defined.

The Tenants List is a table in which each row represents one of your organization’s currently defined tenants (see Tenancy Structure). The table includes the following columns:

• Enabled: Indicates whether the tenant is currently active (checkmark) or inactive.
• Name: The name of the tenant and the tenant's description (if provided when the tenant is configured).
• Package: The name of the package, if any, assigned to this tenant (see Tenants and Packages).
• Views: The number of views assigned to this tenant, either individually or as part of a package (see Tenant View Settings).
• Alert Policies: The number of policies assigned to this tenant, either individually or as part of a package (see Tenant Policy Settings).
• Users: The number of users assigned to this tenant (see Tenant User Settings).
• Last login: The date-time of the last login by any user assigned to this tenant's MKP portal.
• View v4 Tenant Portal (users icon): Takes you to this tenant's MKP portal (see MKP Tenant Portal).
• Remove (trash icon): Pops up a confirmation dialog that allows you to remove the tenant from your collection of tenants.

The Packages tab of the My Kentik Portal page, used to create and manage packages (see Tenants and Packages), is covered in the following topics:

• Packages Tab UI
• Packages List

The Packages tab contains the following main UI elements:

• Filter field: Filters the Packages List to show only the packages whose name or description contains the entered text.
• Add Package: A button that opens the Add Package page (see Package Settings Pages).
• Packages list: A list of the packages currently set up in your organization (see Packages List).
• Package Overview: An information pane at the right of the page that shows information about the packages in use in your organization:
  - Total: The number of packages defined in your organization.
  - Unused: The number of defined packages that haven't yet been assigned to any tenant.
  - With/Without Packages: The number of tenants with packages/without packages.
  - Tenants per Package: A chart showing the number of tenants to which each of the in-use packages has been assigned.

The package list is a set of cards in which each card represents one of your organization’s currently defined packages. Each card includes the following information:

• Icon: The icon assigned to the package.
• Package Name: The name of the package.
• Description: A description of the package.
• Tenants: The number of tenants to which this package has been assigned.
• Policies: The number of policies assigned to this package.
• Views: The number of views assigned to this package.
• Edit: Takes you to the Edit Package page for this package (see Package Settings Pages).
• Remove: Opens a confirmation dialog that allows you to remove the package from your organization's collection of packages.

The MKP Settings page is used to specify settings that are common to all of the tenants in your organization. These settings are specified in a series of tabs accessed via the left sidebar, which are covered in the following topics:

• MKP Domain Settings
• MKP Support Settings
• MKP Branding Settings
• MKP Tenant SSO Settings

The Domain tab of the MKP Settings page is used to set the subdomain that will be included in the URL to which the users added by your tenants will navigate to access your organization’s tenant portal. You specify the subdomain name in the Subdomain field; the rest of the URL is predefined by Kentik as shown in the following example:
https://customer_subdomain.my.kentik.com

Note: If your organization is registered with Kentik in the EU, the above URL will instead end with my.kentik.eu.

The Support Links tab of the MKP Settings page is used to set the email address and URL that users added by your tenants should use when they need support.

• Support Email: The email address at which your organization will provide support for tenant users, and from which emails may be sent to tenant users. Emails auto-generated by the MKP portal may include alerts sent via an email notifications channel as well as invitations sent when the user is added to a tenant.
• Support URL: The URL at which your organization will provide support for tenant users. This support link will be displayed in various locations in the MKP portal and also in emails to tenant users.

The settings on the Branding tab of the MKP Settings page determine the branding elements that are displayed to tenant users of your MKP portal:

• Company Logo: Set an image that will be displayed (in place of the Kentik logo) on the My Kentik Portal login page and on the MKP portal itself:
  - Max file size: 1MB.
  - Supported file types: JPG, PNG, GIF, BMP.
  Notes:
  - For best results, use a logo that will render legibly at a height of 21px.
  - Once an image file has been uploaded a thumbnail of the image will appear to the right of the Logo setting.
• Hide Kentik Branding: Indicates whether Kentik will be mentioned in the UI of your MKP tenant portal. By default the setting is off (mentions of Kentik are not hidden).
  Note: This setting is actually made by the Kentik Customer Support team in response to a request from your organization to license the Advanced MKP Package, which allows unlimited MKP tenants. Once it is turned on it can only be reverted by dropping that package.

When one or more tenants exist in your organization you have the option of enabling the users assigned to those tenants to access your My Kentik Portal via SSO (see About SSO), which you do from the Tenant SSO tab of the MKP Settings page. The settings on this page are nearly identical to the SSO settings for direct (non-tenant) users, which are covered in Kentik SSO Configuration.

The settings pages for tenants are covered in the following topics:

• About Tenant Settings
• Tenant General Settings
• Tenant Data Sources
• Tenant User Settings
• Tenant View Settings
• Tenant Policy Settings

Tenant settings are used to configure and manage the MKP portal for an individual tenant, thus determining what Kentik-derived status and performance information will be presented to that tenant's users (see Tenancy Structure). Settings for a given tenant may be accessed in the following ways:

• Add Tenant: If the tenant doesn't already exist in your organization you'll add the tenant via the Add Tenant button on the Tenants Tab of the My Kentik Portal page, which takes you to an Add Tenant page.
• Edit Tenant: If the tenant already exists in your organization you can edit the tenant's settings on the Edit Tenant page for that tenant, which you reach by clicking on the tenant in the Name column of the Tenants List on the My Kentik Portal page.

The Add Tenant page and the Edit Tenant pages, which we refer to collectively as "tenant settings pages," both contain the same structure, layout, and settings. These pages effectively function as wizards on which settings are specified in sequence on a series of tabs. You can navigate the tabs out of order using the tab names in the left sidebar, but you can't save your changes unless all required settings are specified.

The General tab of the tenant settings pages contains the following settings and controls:

• Name (required): The name by which the tenant will be listed in the Tenants List.
• Description: A description for the tenant.
• Tenant Status: A switch that lets you enable or disable the MKP portal for this tenant. Disabling a tenant allows you to keep that tenant configured while blocking their access to the MKP tenant portal.
• Cancel (Add Tenant only): Click to go back to the My Kentik Portal page without saving any of the settings made while on the tenant settings page.
• Next: Click to advance to the next tab of the page. This button appears only when all required settings on the tab have been specified.

The Data Sources tab of the tenant settings pages enables you to indicate the parts of your network about which this tenant will be able to access network data. The effect is to define a partition of the data set representing your flow records (device or cloud) and give the tenant's users access only to that partition. You can indicate this in one of the following ways:

• Data sources only: Enable tenant access based only on data sources.
  Note: Typically used only when each data source handles flow records from a single tenant.
• Data sources plus filtering: Enable tenant access based not only on data sources, but also on additional factors such as interfaces, what source and/or destination IP ranges they use, their ASN(s), and any Custom Dimensions you've created that could be used to identify a specific tenant.

Note: Kentik recommends assigning a unique label (see Labels) to the data sources associated with each of your tenants. If you use the label for a given tenant to specify the data sources for that tenant in the MKP Data Sources dialog then as you change (add or remove) the data sources to which the tenant's label is applied the MKP data sources for that tenant will automatically change as well.

The Data Sources tab contains the following settings and controls:

• Data Sources: Radio buttons that you use to indicate how you'd like to identify the parts of your network for which this tenant will be able to see network data:
  - Simple: You'll choose the data sources for this tenant from a Data Sources dialog that you open with the Edit Data Sources button in the Choose Data Sources pane. The Apply Filtering Criteria pane will be hidden.
  - Advanced: You'll choose the data sources for this tenant from the Data Sources dialog but you'll also apply filters on ASNs, IPs, etc. using the Apply Filtering Criteria pane, which will be shown.
• Edit Data Sources: A button that opens a Data Sources Dialog from which you choose the devices and clouds from which this tenant will be able to see network data. Your currently selected data sources (if any) are listed just above the button.
• Apply Filtering Criteria (shown only when Data Sources is set to Advanced): A form that enables you to use filters to narrow the network data this tenant will be able to see from the selected data sources (see Apply Filtering Criteria Pane).
• Save: A button that enables you to save the current tenant settings. If the button is not active, hover over it to pop up a message indicating which required fields are still incomplete.

The Apply Filtering Criteria pane is used to specify filters that narrow the network data this tenant will be able to see from the data sources selected in the MKP Data Sources dialog. The fields for each filter setting will be ANDed, but if a field allows entry of multiple values (e.g. CIDRs, ASNs) then those values will be ORed.

The pane includes the following fields and controls:

• Show Tenant Filter: A button that pops up a detail of all filters currently applied in the Apply Filtering Criteria pane.
• Interface: Specify regular expressions (regex) to match against the following fields of interfaces on the devices selected with the Data Sources dialog.
  - Interface Name: Traffic will be matched based on the vendor-defined name (e.g. “GigabitEthernet0/1”) of the device interface (physical or logical) through which flow ingressed/egressed.
  - Interface Description: Traffic will be matched based on the user-provided description (e.g. “Connected to upstream ISP”) of the device interface (physical or logical) through which flow ingressed/egressed.
• CIDR(s): Enter a comma-separated list of one or more IP CIDRs. Traffic will be matched based on interfaces with the entered IP/CIDR address range.
• ASN(s): Enter a comma-separated list of one or more ASNs. Traffic will be matched based on the origin ASN associated with the source/destination IP of the flow.
• Add (Custom Dimensions): A button that shows a pair of drop-downs to use for Filtering with Custom Dimensions:
  - Dimension: Choose the custom dimension name.
  - Populator: Choose a populator from selected custom dimension.

The following considerations apply when using custom dimensions for MKP tenant filtering:

• Multiple dimension/populator pairs may be used simultaneously.
• The custom dimension(s) to match on must already be defined in your organization (see Custom Dimensions).
• The specific attributes used by a custom dimension to attribute flows to different tenants will vary depending how your network is organized.
• The value that is inserted into the custom dimension's flow record field at ingest should allow you to uniquely identify each tenant (e.g. tenant name), so that you can tell which traffic is associated with each tenant.
• If a custom dimension is specified for MKP data source filtering (e.g. Tenant_DST) and that same dimension is also used as a filter dimension in a dashboard panel that is included on a view that you make available to tenants, then the populator value specified in each tenant's MKP filtering settings will override the value of the same populator in the panel filtering. This enables you to use a given panel for multiple tenants while ensuring that the traffic shown in the panel is specific to each tenant.

The Users tab of the tenant settings pages contains the following settings and controls:

• Add User: A button that pops up a dialog in which you enter the name and email address of the user, which initiates the MKP User Activation.
• User list: A table listing the users of this tenant.
  - Name: The name of the user.
  - Email: The user's email address.
  - Last Login: The date-time of the most recent login by this user to the tenant's MKP portal.
  - Remove: A button that pops up a confirming dialog that enables you to remove the user.
• Save: A button that enables you to save the current tenant settings. If the button is not active, hover over it to pop up a message indicating which required fields are still incomplete.

When a user is added to an MKP tenant, the account activation process involves involves the following steps:

1. Add the user with the Add Users button on the Users tab of a tenant settings page (see Tenant User Settings).
2. An invitation email will be sent to the email address that was entered for the user. Click the Activate your account button in the email.
3. On the resulting Account Activation page enter (and confirm) a password.
4. When the account has been activated, click the Return to Kentik link, which goes to the login page for the MKP tenant portal.
5. Enter credentials and log in.

The Views tab of the tenant settings pages enables you to determine what views — Dashboards and Saved Views (see About the Library) — in your organization will be visible to this tenant's users. You can make your organization's views available to your tenants in the following ways:

• By package: Choose a package (see Tenants and Packages) from the horizontal Select a Package list across the top of the tab.
• Individually: Choose a view from the categorized Available list at the left of the tab.

When a view is chosen, either individually or as part of a chosen package, it is removed from the Available list and added to the Selected Views & Dashboards list at the right of the tab. In the screenshot below, for example, the Selected Views & Dashboards list shows two views selected individually and 10 views selected because they are part of a package that this has named "Gold," which includes five views from a package named "Silver" plus five additional views. The Available list, meanwhile, shows (by category, some of which are collapsed) the views that are still available to be selected.

The Views tab contains the following settings and controls:

• Select a Package: A list showing all of your organization's current packages, plus No Package (default). Click a package to add that package's views to the Selected Views & Dashboards list.
  Note: Currently each tenant can be assigned only one package at a time.
• Manage Packages: A button that takes you to the Packages Tab of the My Kentik Portal page.
• Available: A categorized list of your organization's views (Dashboards and Saved Views) that aren't yet selected for this tenant. The categories match the categories used in the Views list in the Library. Click the Plus icon (+) at the right of a given view to select it. The view will be moved from the Available list to the Selected Views & Dashboards list.
• Selected Views & Dashboards: A categorized list of the views that your organization currently has assigned to this tenant, either individually or via a package. Click the Minus icon (-) at the right of a given view to unselect it; it will return to the Available list.
• Save: A button that enables you to save the current tenant settings. If the button is not active, hover over it to pop up a message indicating which required fields are still incomplete.

Note: To see an individual view in the Available list or the Selected Views & Dashboards list as it would appear to a given MKP tenant, click the name of that view (see Preview as Tenant).

Preview as Tenant enables you to see an individual view (Dashboard or Saved View) as it would appear to a given MKP tenant. The settings configured for the tenant by the Data Sources selector and the Apply Filtering Criteria pane on the Data Sources tab of the tenant settings pages are applied in the preview as a filter named after the tenant, which results in the view showing only the traffic data that has been configured for that tenant.

You can access a tenant preview in the following ways:

• On the Views tab of the tenant settings pages (see Tenant View Settings), click the name of an individual view in the Available list or the Selected Views & Dashboards list, which will take you to the tenant-filtered view.
• In Data Explorer, choose Preview as Tenant from the Actions menu (see Data Explorer Actions), then choose the tenant for the preview, after which you'll be taken to the tenant-filtered view.
• In the Library, on a Dashboard (see Dashboard SubNav Controls) or Saved View, choose Preview as Tenant from the Actions menu, then choose the tenant for the preview, after which you'll be taken to the tenant-filtered view.

Note: Preview as Tenant is a preview of one specific view. To preview a tenant's entire MKP tenant portal (see MKP Tenant Portal) as if you were that tenant, use the View v4 Tenant Portal link in the Tenants List.

The Policies tab of the tenant settings pages enables you to configure policies for alerts that will notify the tenant's users of anomalous conditions affecting their network traffic.

Note: These "tenant-specific" policies are in addition to any policies that have been assigned to a tenant via a package (see Package Policy Settings).

The Policies tab includes the following UI elements:

• Add Alert Policy: A button that opens a new Policy card, which will appear in the Policy list.
• Policy cards: One or more cards that each represent a policy (see Alert Policy Cards).
• Policy list: A set of vertically arrayed Policy cards followed at bottom by the Add Alert Policy button. The list will be empty (except for the button) if no policies have been assigned yet to this tenant.

Each Policy card contains the controls needed to specify one alert policy. In it's initial state the card will contain these controls:

• Policy: A drop-down menu from which to choose an alert policy to make available to this tenant. The menu will be populated with all alert policies currently existing in your organization, which you can find by clicking the Configure Alert Policies button on the Alerting page (Protect » Alerting).
• Remove button: Click the X to remove the policy.

Once a policy has been chosen from the Policy list the following additional controls appear, allowing you to configure the policy for this tenant:

• Hide/Show Thresholds: A button that toggles visibility for the threshold controls for this policy.
• Policy description: The description assigned to the policy in the General Settings tab of the policy itself (see General Policy Settings).
• Thresholds list: A list of the thresholds defined in the policy (see About Alert Thresholds). For each threshold there is a list of one or more Conditions, with operator and value settings for each condition. These settings default to the settings defined in the Conditions pane of the Alert Thresholds tab of the policy itself (see Threshold Conditions). You can change the settings to customize the policy for this tenant.
• Enable Notifications: A switch that adds a Notifications tile to the threshold (see Threshold Notifications), so that you can specify alert notifications that will be sent to either the tenant or landlord.
  Note: Tenant notification settings require spoofing the tenant in the MKP tenant portal; see Tenant Notifications Access.

The Notifications settings specify the situations in which one or more match (see About Matches) will cause a threshold to trigger an alarm (enter ALARM state) and generate notifications.

The following settings specify what triggers an alarm:

• Number: How many times a match must occur within the specified duration.
  Note: If number is 1, the time settings are irrelevant; an alarm will be generated immediately upon the first match.
• Duration value: The number of time units.
• Duration units: The time unit, either minutes or hours.
• Reset period: The number of match-free minutes after which the count of matches is reset to 0.

The following settings configure notifications for the tenant landlord (your organization):

• Receive Landlord Notifications: Enable receipt by the landlord of tenant-level threshold notifications, which would otherwise go only to the tenant.
• Notification Channels: Click in the field to choose from a list of the existing notification channels in your organization.

The settings page for tenants is covered in the following topics:

• About Package Settings
• Package General Settings
• Package View Settings
• Package Policy Settings

Package settings are used to configure and manage packages, which are named collections of views (Dashboards and Saved Views) and Alert Policies (which define traffic conditions in which tenant users may receive notifications). Settings for a given package may be accessed in the following ways:

• Add Package: If the package doesn't already exist in your organization you'll add the package via the Add Package button on the Packages Tab of the My Kentik Portal page, which takes you to an Add Package page.
• Edit Package: If the package already exists in your organization you can edit the package's settings on the Edit Package page for that package, which you reach by clicking on the Edit button in the Packages List on the My Kentik Portal page.
  Note: Any changes made while editing a package will be all applied to all of the tenants assigned to that package. Kentik recommends notifying tenants of any significant changes.

The Add Package page and the Edit Package pages, which we refer to collectively as "package settings pages," both contain the same structure, layout, and settings. These settings are specified in a series of tabs accessed via the left sidebar.

The General tab of the package settings pages contains the following settings and controls:

• Default: A switch that, if enabled, will result in this package being assigned automatically to new tenants.
• Name (required): The name by which this tenant will be listed in the Tenants List.
• Description: A description for the tenant.
• Icon: A drop-down containing icons that you can use to represent this tenant in
• Color: A drop-down from which you can choose a color to associate with the this tenant, either by clicking a preset swatch or entering a hex color code.
• Preview: A rendering of the icon/color combination resulting from the current settings.
• Save: A button that enables you to save the current package settings. If the button is not active, hover over it to pop up a message indicating which required fields are still incomplete.

The Views tab of the package settings pages enables you to determine what views — Dashboards and/or Saved Views (see About the Library) — in your organization will be visible to the users of the tenants to which this package is assigned. You make a given view available in a package by choosing it from the categorized Available list at the left of the tab, which shows the views that are available to be selected. Once selected, the view is removed from the Available list and added to the Views in Package list at the right of the tab.

The Views tab contains the following settings and controls:

• Available: A categorized list of your organization's views (Dashboards and Saved Views) that aren't yet selected for this package. The categories match the categories used in the Views list in the Library. Click the Plus icon (+) at the right of a given view to select it. The view will be moved from the Available list to the Views in Packages list.
• Views in Package: A categorized list of the views that your organization currently has assigned to this package. Click the Minus icon (-) at the right of a given view to unselect it; it will return to the Available list.
• Save: A button that enables you to save the current package settings. If the button is not active, hover over it to pop up a message indicating which required fields are still incomplete.

The Policies tab of the package settings pages enables you to configure alerts that will notify about anomalous conditions affecting network traffic. When a threshold is triggered in a package-level alert policy the specified notifications will go to the MKP users of all tenants to which the policy is assigned, whether directly or via a package. The settings and controls for package-level alert policies are identical to those for tenant-level policies, which are covered in Tenant Policy Settings.

Configuring tenancy involves the steps detailed in the topics below:

• Configure Tenant Portal
• Add a Tenant
• Edit a Tenant
• Add a Package
• Edit a Package

To configure a tenant portal:

1. On the My Kentik Portal page, click the Settings button at upper right to go to the MKP Settings Page.
2. On the Domain tab, set the subdomain for your organization’s tenant portal (see MKP Domain Settings).
3. On the Support Links tab, set the email address and URL that tenant users should contact when they need support (see MKP Support Settings).
4. On the Branding tab, set the logo that will appear on the tenant portal (see MKP Branding Settings).
5. To enable SSO, fill in the SSO settings on the Tenant SSO tab (see MKP Tenant SSO Settings).
6. Click the Save button to save the tenant portal configuration.

To add a tenant:

1. On the Tenants Tab of the My Kentik Portal page, click the Add Tenant button to go to the Add Tenant page (see Tenant Settings Pages).
2. On the General tab, provide a name and description for the tenant (see Tenant General Settings).
3. On the Data Sources tab, specify the parts of your network about which this tenant will be able to see network data (see Tenant Data Sources).
4. On the Users tab, specify the users that will have access to this tenant's MKP portal (see Tenant User Settings).
5. On the Views tab (see Tenant View Settings):
   - Choose which package, if any, to assign to this tenant.
   - Choose any additional views (Dashboards or Saved Views) to make available to the users of this tenant.
6. On the Policies tab, specify the alert policies whose notifications will be received by users of this tenant (see Tenant Policy Settings).
7. Click Add Tenant to save the settings and exit the dialog. The new tenant will appear in the Tenants List.

To edit a tenant:

1. In the Tenants List on the Tenants tab of the My Kentik Portal page, find the tenant that you’d like to edit (if desired, use the Filter field).
2. Click on the tenant name in the Name column to open the Edit Tenant page.
3. Modify one or more settings as described in Add a Tenant.
4. Click Save to save the settings and exit the dialog.

To add a package:

1. On the Packages Tab of the My Kentik Portal page, click the Add Package button to go to the Add Package page (see Package Settings Pages).
2. On the General tab (see Package General Settings), provide a name and description for the package. If desired specify a new color and/or shape for the package icon.
3. On the Views tab (see Package View Settings), choose which views (Dashboards or Saved Views) to make available to the users of this package.
4. On the Policies tab, specify the alert policies whose notifications will be received by users of this package (see Package Policy Settings).
5. Click Add Package to save the settings and exit the dialog. The new package will appear in the Packages List.

To edit a package:

1. In the Packages List on the Packages tab of the My Kentik Portal page, find the package that you’d like to edit (if desired, use the Filter field).
2. At the right of the package's tile, click on the Edit button, which opens the Edit Package page for that package.
3. Modify one or more settings as described in Add a Package.
4. Click Save to save the settings and exit the dialog.