Lineaje Learning Center
  • About Lineaje
  • Lineaje Product Offering
  • Getting started
    • Create an account
      • Configure Azure AD for sso
      • Configure Okta for sso
    • Onboarding workflow
  • SBOM360, OSM
    • Generate an SBOM
      • Source Code Management (SCM) As Source
        • Public Code Repositories
        • Private Code Repositories
          • Configure GitHub credentials
          • Configure Bitbucket credentials
          • Configure Gitlab credentials
          • Configure Git credentials
          • Configure Azure Repo
        • Frequently Asked Questions
      • Container Image As Source
        • Public Container Image
        • Private Container Image
          • Configure AWS Elastic Container Registry
          • Configure Google Container Registry
          • Configure Docker Hub
          • Configure Generic OCI Registry
          • Configure Azure Container Registry
        • Frequently Asked Questions
      • Existing SBOM As Source
        • EO 14028 checks
      • Manifest file As Source
      • Android Package Kit (APK)
      • Using Lineaje CLI
    • Explore Your SBOM
      • Info
      • Attestation
      • IRL
      • Dependencies
      • Provenance
      • Vulnerabilities
      • Mitigations
      • Security Posture
      • Code Quality
      • Suppliers & Licenses
      • Findings
    • Manage Your SBOM
    • Dashboard
    • Search
    • Policies and Gates
    • Organization and User Management
      • Organization example
    • Lineaje AI
    • AI Plan and AI Remediate
      • JIRA Integration
  • SBOM360 Hub
    • My Products
    • My SBOMS
    • Find & Review SBOMs
    • Manage Your Repository
    • Request and Share SBOMS
    • Settings
    • User Roles
  • Lineaje CLI
    • System Configuration
    • CLI Installation
    • CLI Usage
    • Troubleshooting CLI issues
    • Support matrix
  • Integration with CICD pipeline
    • Pre-Requisites
    • Generate Project from source code
      • Project creation using Lineaje cloud
  • Abbreviations and Descriptions
  • Release Notes
    • Unified Scanner for AWS
Powered by GitBook
On this page
  • Tenant Admin/ Org Admin onboarding workflow
  • Function User Workflow
  1. Getting started

Onboarding workflow

PreviousConfigure Okta for ssoNextSBOM360, OSM

Last updated 1 year ago

On first login, you will be presented with an onboarding workflow. The onboarding flow is different for a Tenant Admin, Org Admin and a Function User.

Tenant Admin/ Org Admin onboarding workflow

The onboarding flow will guide you to setup child organizations (optional), setup additional gates (optional), invite users to create policies for gates, invite users to create integrations.

  1. Global Organization

By default, a root organization will be created for you. All users will belong to this root organization. In this step, you can change the name of the root organization. You are the tenant admin and you will be the org admin for this root organization.

  1. Gates

The second step is to create additional gates. As a tenant admin, you can create gates that you want your entire org to be evaluated against. For e.g., it could be a gate related to open source vulnerabilities or it could be a gate related to open source provenance or it could be a gate related to usage of specific license or it could be a gate related to usage of components from a particular vendor and so on.

Gates are inherited. So a gate that is assigned to an org will be applied to the SBOMs in that org and all of its sub orgs. You can learn about gates Policies and Gates.

The default gates are already applied and show up.

  1. Child organization

Creating child organizations is an optional step. By default all users belong to the default root organization.

You can create child organizations. Organizations may map to a team, BU, product team etc. You can create orgs and sub-orgs that can map to your company. Organization decides the visibility and ownership of SBOMs.

  1. Setup integrations

The last step is to setup integrations. In this step, you can configure the tokens necessary to access the source repository, image repository. Once configured, this can be used for SBOM generation.

Function User Workflow

The teannt Admin/Org Admin could have delegated the policy setup and/or integration setup to function users. When a function user logins for the first time, an onboarding flow will show up to guide the user on the tasks.

  1. Your Roles

This step gives the information about the roles assigned to this function user.2

  1. Your Organizations

This step gives the information about the organizations to which the fucntion user belongs to.

  1. Assigned Tasks

This step lists the assigned (delegated) tasks to the user. This will list the delegated tasks - setup policy or setup integrations or both.

  • Clicking on "Create Policy" will take the user to the Policy page

  • Clicking on "Setup Integration" will take the user to the Integrations page