The Resp Org IDs that you have access to the ROC System within the TFNRegistry™ are based upon the Cross Entity permissions (also known as the "Acting As" feature) established in your profile. Cross Entity permissions can be managed for you by your Resp Org’s Primary Contact and/or Company Administrator(s) on the Somos Portal Website (portal.somos.com).
Currently, the ROC permissions are at Entity level (e.g. ZA***). Beginning, Sunday, October 29, 2023, the ROC System within the TFNRegistry will use the update Resp Org ID (e.g. ZATST, ZATS1, etc.) permissions list from your profile just like the rest of the TFNRegistry. This will change the behavior of the ROC permissions. Please Note: The update Resp Org ID permissions list for your profile will be shared across the ROC System and the rest of TFNRegistry.
If the Login ID is used only for accessing ROC System within the TFNRegistry, then the update Resp Org ID permissions list can be updated to the Entity level permissions to retain the existing level of access and maintain backwards compatibility. On Sunday, October 29, 2023, this will automatically be taken care of for existing ROC only Login IDs.
If the same Login ID is used for both the ROC System and the TFNRegistry, then the existing update Resp Org ID permissions list should be expanded to include Entity level permissions for your Resp Org ID. If you already have Entity level permissions, no action is required. This will also provide TFNRegistry access at the Entity level. If you do not want to expand permissions in the TFNRegistry or you want to maintain a different level of access for both the ROC System and the TFNRegistry and maintain backwards compatibility, two different Login IDs should be utilized.
For more information on how to get started with the Acting As feature for Cross Entity ROC Permissions, please click here.