By hovering over the username at the top right hand corner of the FOSSA application, a user may navigate to Settings > Organization to reach the Organization Settings. Here a user may manage Teams, RBAC, Users, Default project settings, and Authentication
Here a user may manage general organization settings. Please see the table below for detailed breakdown
|Title of organization used in reports such as attribution or SBOMs
|Email used for all billing related communication
|Default New User Role
|The default role applied to any new user invited to your organization
|Labels allow for adding user-defined metadata on projects. They can be used to filter projects on pages such as Projects, Global issues, Packages, and Global reports.
|Internal Component Signatures
|Specify signatures for marking internal component naming conventions. FOSSA will recognize any component that contains these signatures in their names as internal dependencies and will ignore these dependencies
|Emails a contributor report of detected contributors for analyzed projects, broken into weekly increments
Manage new and existing teams including users/members, projects, and default team roles. Please see Teams & Roles (RBAC) for more details.
Manage default and customer roles for RBAC as well as individual permissions. Please see Teams & Roles (RBAC) for more details.
Manage and invite users to your organization as well as their RBAC & Team associations. Please see Inviting Users for more details
Manage default project settings across your organization. For each settings group, such as Security, Licensing, or Quality settings, you have two options,
By saving changes made to Default Project Settings, any new projects imported into FOSSA will begin using the new Default Project Settings. Any existing projects will maintain their current Default Project Settings.
If a user would like to push or "propagate" the current default project settings the user must select
propagate settings and select which settings to propagate.
For example a user may want to change security policy settings for all projects without changing the licensing policy used on each project. Here a user would:
- Select a new security policy and
propagate settingsand choose
override all project to use security policy "Some Security Policy"
Now all existing and new projects will use the new security policy, however any existing projects will continue to use their individual licensing policy.
This is a change from the previous
Propagate and Make Defaultorganization settings options. This change allows for granular control for default project settings.
Manage authentication settings for your organization including SSO & SAML Identity providers. Please see Single Sign On for more details.
Updated 21 days ago