The Tessl Registry now has security scores, powered by SnykLearn more
Logo
Back to articlesTessl Admin Guide: Organizations, Workspaces, and Roles

11 May 20265 minute read

Shawn Miller

Technology enthusiast.

Just signed up to Tessl? Wondering next steps to rolling Tessl out to your team? The following article will take you through the steps of managing your top level Organization, invite your users, set policy items, then create your workspaces, assigning membership to those workspaces and defining their roles.

How Organizations and Workspaces work in Tessl

Organizations are top level entities, often representing the billing or corporate entity, with a subcategory called Workspaces that provide role-based access to the various users across the company.

A diagram showing a top level Organization, with many workspaces below. Some with Search,Install, and Publish permissions, some with just Install and Publish, and one with no access.

Setting up your Tessl Organization

Organizations are sometimes created during the presales phase of acquiring Tessl, or may be created later. If one has not been created, it will be auto created when you create your first workspace. If prompted, click Create workspace and name it after your team (i.e. Engineering) to start.

View of the registry page where a Create workspace button is being discplayed.

The default organization and workspace should now be visible from the main interface:

When the first workspace is created, a default organization will be displayed. This can be edited.

Once created, navigate to Settings for your Organization, rename the organization to your company name and specify if users can publicly share skills by enabling the button.

Organization settings displayes an organization name, the ability to save, and an option to block public tile publishing by toggling a selector.

Creating and managing Users in Tessl

Next, invite users to your organization, by navigating to the Organization’s Members menu, assigning the workspaces the users will have access to. Users will be created with the Organization
members role, able to see, search and install skills from the chosen workspaces. Permissions can be promoted from the Workspace Members menu, which will be discussed later below. Users will need to accept the invite they are sent.

Invite member screen displayes an email address, a selection of workspaces that can be added to the user specified.

Once created, you can elevate a user to Admin to allow workspace creation or manage users. To do so, navigate to the Organization Members screen, and click the three dots under Actions. Assign an appropriate role. Examples will be provided below of some common configurations.

Expanding the options menu, which is three dots, next to each name yields a submenu with change role and remove

Admin keys

image.png

Admin keys are for integrations and applications where programmatic access is required across workspaces. This is typically used for automation purposes and an expiration can be set up to one year.

Managing Workspaces and Users in Tessl

On the side menu of the screen, users can select all plugins, eval runs, projects and members from a specified workspace.

Click the workspace drop-down to create new workspaces. Navigate to Members at the workspace level to specify Roles for users who require more capabilities within the workspace, such as running evaluations, publishing or managing users.

To modify a user, search for their name, select their checkbox, a role, and click the Add button.

The role selector allows user to select consumer, member, publisher, manager and owner when adding a user to a workspace.

Example role configurations for your team(s)

The following users demonstrate common configurations and roles that may be used when rolling Tessl out:

Samira - Org. Admin

Samira, the administrator and skills champion, needs the ability to manage all workspaces, the ability to assign users, and create new workspaces. Make her an Organization admin.

A diagram showing Samira with admin privileges at the Organization level , giving her full permissions on the workspaces below as a result

Eddie - Lead Engineer

Another user, Eddie, might be a member of an engineering workspace. He needs to be able to use plugins (skills) that have been published, but may need to have access to publish skills within the engineering workspace for others on his team. This could mean Eddie is the publisher role in certain workspaces. He may also be a Member role of other workspaces where he only needs to search and install from.

A diagram showing an organization with several workspaces. The user has publisher permission on several, giving search. install, and publish rights. Several other workspaces the user is only a member, providing more limited permissions like Search and Install. One workspace is no access because they were not given permissions.

Joe - New hire engineer

Finally, Joe, a new hire, has the ability to search and install skills from the engineering workspace, but does not have the ability to share/create skills until later, after they’ve gained a little more experience. Joe would be made a member of “engineering” with just a “consumer” role.

Next steps!

Now that you have your users in, and assigned roles to the different workspaces, you and your users can:

  • Start creating new skills
  • Evaluate new or existing skill effectiveness through using Reviews, and Evals
  • Publish those skills to the Tessl registry to share them for your users and agents

Let us know what you think! Tessl would love to hear from you through any one of our feedback channels (Discord, Email, CLI Feedback, etc)