[Upcoming] Deprecation of Limited Access Members (LAMs)

English Forum Developers & API Changelog
, , ,
1

Summary

We’re deprecating Limited Access Members (LAMs) to simplify team membership and improve security. LAMs are users who currently receive limited team access implicitly through project membership, without being full team members. Starting in October 2025, this automatic team access will be removed. This change is an important milestone for removing the association between teams and projects which we previously announced here.

This change affects team and project membership API endpoints. The API interface is not changing and existing integrations will continue to work, but some users will no longer appear as members of teams where they did previously.

Who is affected

This change impacts developers whose applications:

  • Query team memberships or team member lists
  • Rely on LAMs appearing in team-related API responses
  • Rely on a user being automatically added to a team if they are added to a project that belongs to that team.

If your integration processes team membership data, you should review and potentially adjust your logic to handle the removal of LAM-based team memberships.

API Behavior Changes

The following endpoints will no longer return LAM-based team memberships:

  1. GET /users/{user_gid}/teams
  2. GET /users/{user_gid}/team_memberships
  3. GET /team_memberships
  4. GET /teams/{team_gid}/team_memberships

The following endpoints will no longer automatically create or remove LAM-based team memberships as a side effect:

  1. POST /memberships - Adding a user to a project
  2. POST /projects/{project_gid}/addMembers
  3. POST /projects/{project_gid}/addFollowers

The end result is that users may appear to be a member of fewer teams and teams may appear to have fewer members.

Migration Steps

  1. Audit your integrations: Review code that processes team membership data
  2. Test with reduced data: Prepare for fewer team memberships in API responses
  3. Update logic: If you rely on a user implicitly added to a team as they are added to a project, consider explicitly adding the user to a team going forward. (And note that, in the future, projects will not be associated with teams.
  4. Handle missing memberships: Add error handling for team memberships that may no longer exist

Timeline

  • October 2025: LAM deprecation begins - gradual deployment per Asana domain

Why we’re making this change

LAMs created complexity in our permission model and could lead to unexpected access patterns. By removing automatic team access through project membership, we’re creating a clearer, more predictable membership model that gives administrators better control over team access.

This change is an important milestone for removing the association between teams and projects which we previously announced here.

Questions and Feedback

If you have questions about how this change affects your specific integration, please let us know! We’re particularly interested in feedback about any edge cases or challenges you encounter.

5 Likes