Organization Users

Manage your team members and their access to Silkline.

Default Role for New Users

You can set a default role for new users. Any new user added to the organization will automatically be assigned this role when they join the organization.

Changing the default role only applies for new members going forward.

User List

The user list shows all active members, their roles, and their current status. Use the ⋮ menu to manage individual users (e.g. resend invite, deactivate).

User statuses

Status
Description

Member

The user has accepted their invitation and has an active account in your organization. They can sign in and use Silkline based on their assigned role.

Pre-registered

The user was added through an integration or bulk import, but has not yet been invited to log in. You can send them an invitation at any time.

Invited

The user has been sent an invitation to join your organization but has not yet accepted it. Their account will be activated once they accept the invite.

Invite expired

The user was invited but did not accept the invitation within the expiration period. You can resend the invitation to allow them to join.

Inactive

The user's account has been deactivated. Inactive users cannot log in or access the platform. Use the Show Inactive toggle at the top right to view users who have been deactivated.

User roles

Silkline currently offers the following predefined roles:

Viewer
  • Purpose: Provides read-only access to Silkline.

  • Permissions: Users with the Viewer role can see information like requests, quotes, orders, and suppliers within Silkline, but they cannot create, edit, delete, or send anything.

  • Ideal Use Case: Suitable for stakeholders, managers, or team members who need visibility into procurement activities but don't actively participate in the workflows.

Collaborator
  • Purpose: Designed for users primarily involved in the sourcing process (e.g., engineers, requesters).

  • Permissions: Collaborators can actively work on sourcing tasks. They can:

    • Create and edit Requests (RFQs).

    • Create, edit, and delete Quotes received from suppliers.

  • Limitations: Collaborators cannot manage or send purchase orders, send requests/check-ins, or manage supplier information.

  • Ideal Use Case: Team members who define requirements, create RFQs, and evaluate supplier quotes but do not handle the final purchasing or supplier management.

Material Planner
  • Purpose: Designed for users responsible for managing order status, material availability, and delivery timelines.

  • Permissions: Material Planners can do everything Collaborators can, plus:

    • Edit and create Parts

    • Send Check-ins to suppliers

  • Limitations: Material Planners cannot manage or send purchase orders or manage supplier information.

  • Ideal Use Case: Team members focused on ensuring suppliers deliver on time and maintaining up-to-date information on open orders.

Supplier Quality
  • Purpose: Designed for users managing supplier relationships, quality requirements, and compliance without handling purchase orders.

  • Permissions: Supplier Quality users can do everything Collaborators can, plus:

    • Create, edit, and delete Suppliers and Supplier Tags.

    • Create, edit, and delete Quality Clauses.

    • Create, edit, and delete Pedigrees.

    • Create, edit, and delete Terms & Conditions.

  • Limitations: Supplier Quality users cannot create, edit, or send purchase orders.

  • Ideal Use Case: Quality engineers, supplier development specialists, or vendor managers responsible for maintaining supplier information, defining quality requirements, and managing compliance without procurement authority.

Buyer
  • Purpose: Offers comprehensive access to manage end-to-end procurement workflows.

  • Permissions: Users with the Buyer role have the broadest access. They inherit all Material Planner permissions and can also:

    • Create, edit, and send Purchase Orders.

    • Send Requests (RFQs) and Check-ins to suppliers.

    • Create and manage Supplier profiles and related information (including tags).

    • Create and manage Parts within Silkline.

    • Define and manage Quality Clauses.

    • Manage Request Tags.

    • Create, edit, and delete Pedigrees (documentation of product origin and chain of custody).

    • Configure certain Organization Settings, Custom Fields, and the Organization Chart.

  • Ideal Use Case: Procurement professionals, purchasing managers, or administrators responsible for the full procurement lifecycle, from sourcing and ordering to supplier relationship management and system configuration.

Admin
  • Purpose: Provides full access to your Silkline organization, allowing the management of all resources and users. Only a Silkline administrator can assign a user to this role.

  • Permissions: Admin is the highest level of access. It inherits all Buyer permissions (including creating, editing, and deleting Pedigrees) and can also:

    • Assign roles to other users in the organization

    • Set the default role assigned to new users

  • Ideal Use Case: Assign to the user(s) responsible for managing Silkline access and usage, so that they can assign appropriate roles to other users.

Single Sign-on

User management works a little differently for users with Single Sign-on (SSO) enabled:

  • User access is controlled within your Identity Provider (IdP) (e.g. Okta, Azure AD, Google Workspace). Anyone who is authorized for the Silkline application in your IdP can sign in to Silkline without needing a manual invitation.

  • New users in Silkline are typically created automatically the first time they sign in through your SSO provider (e.g. Okta, Azure AD), even if they weren't manually invited in Silkline.

  • These users will appear as Member once they've successfully authenticated.

  • Pre-registered users added via bulk upload or integrations can still be invited if needed, but in many cases they can simply log in via SSO to activate their account.

  • For SSO users, Inactive status in Silkline affects visibility only. Inactive users are hidden from user selections and cannot be newly assigned to items, but their ability to sign in remains controlled by your Organization's IdP. To block sign-in, remove or revoke access in your IdP.

Last updated