Understanding Extended Trial (ET) / Temporary 30-Day Licenses and Default Permissions in Jama Connect®

Chris
Chris
  • Updated

Published Date: May 6, 2026
Audience: Everyone
Products and Versions Covered: 

  • Jama Connect® 

Summary

This article explains when Jama Connect® grants an Extended Trial (ET) / Temporary 30-day license, the common workflows that create these users, and the access and permissions these users have by default. It also clarifies that licenses and permissions are separate: the ET license indicates a temporary licensing state, while the user’s ability to access projects/items depends on explicit permission assignments (for example, via group membership).

Symptoms / Common Questions

  • “A new user logged in via SSO and got an Extended Trial (ET) / 30-day trial license—why?”
  • “If someone is invited via @mention or review invitation, what license do they get?”
  • “Does an ET / 30-day trial user automatically get access to projects or items?”
  • “Is this a security issue—are permissions granted automatically?”

Resolution

How ET / Temporary 30-Day Licenses Are Granted

Jama Connect® can create new users and assign a temporary license in multiple ways, depending on how your organization is configured.

A) Inviting a Non-User via @Mention (Stream / Comments)

When a Jama Connect® user @mentions a person by email address who is not already a user, Jama Connect® can provision a temporary account and grant limited access for 30 days. This is commonly used to involve external reviewers/stakeholders in a conversation. After 30 days, access is deactivated unless an admin assigns a different license.

Key points:

  • The invited person receives temporary access for 30 days.
  • Access is limited (they can view the comment thread(s) they were invited to and see descriptions of referenced items in those threads).
  • After 30 days, the license expires, and the user is locked out unless the license is converted/updated.

B) SAML / SSO “Auto-Generation” (Auto-Provisioning) for New Users

For Jama Connect® Cloud environments using Auth0 SAML, organizations may enable a configuration that allows Jama Connect® to auto-generate new SAML users when they authenticate through the Identity Provider (IdP). In that case:

  • A user can “self-register” via the IdP.
  • The new user is granted a 30-day trial license.
  • An Organization Admin must assign the appropriate license and permissions after the user is created.

This is distinct from @mention invitations, because the user is created as part of the authentication/login flow rather than from a collaboration thread.

Default Permissions vs. License Type (Critical Concept)

A user’s license type does not automatically grant project access. Access to projects, components, and sets is governed by permissions assigned by administrators (often through group membership and project permissions).

For Temporary / 30-day trial access specifically, Jama Connect® Help/User Guide language indicates that the only default permissions are limited to the discussion thread or review to which they were invited.

Additionally, Jama Connect® documentation describing Temporary licenses states:

  • Temporary licenses are for non-licensed users to trial Jama Connect® for 30 days.
  • They are available only when a user is invited via email to a review or to comment in the stream.
  • The only default permissions are for the invited discussion thread or review.

What a Temporary / ET User Can Do by Default

Based on documented behavior:

  • They can access the specific review or comment thread they were invited to (and related limited context such as item descriptions in the thread).
  • They do not automatically gain access to projects/items beyond what is explicitly shared through that invitation context.
  • Continued or expanded access requires an administrator to assign an appropriate permanent license and project permissions before the temporary access ends.

Admin Actions / Recommended Practices

  1. Decide how new users should be created
    • If using SAML, confirm whether auto-generation/self-registration is desired (new users can be created upon SSO authentication depending on configuration).
  2. Review newly created trial/temporary users regularly
    • Assign the correct permanent license and explicit permissions before the 30-day period ends.
  3. Security validation
    • Confirm that any access beyond the invited thread/review is coming from deliberate permission assignments (project permissions or group membership), not from the temporary license itself.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.