Organization-scoped endpoints and organization access tokens no longer check the organization’s plan, so requests that previously failed with 403 plan_restricted now succeed. The restriction never applied to every account — organizations that predated it kept access regardless of plan — so you may see no change. Rate limits are unchanged.

Three endpoints still require the plan to include the underlying feature — screenshot settings, app & URL tracking settings, and overtime policies. They now answer 403 with code: "feature_not_available" and error_code: 10006 instead of code: "plan_restricted" and error_code: 10005. If your integration branches on 10005 or on plan_restricted, update it to 10006 / feature_not_available. Code 10005 is retired and will not be reused.