Platform Release Notes 25.02

Crew Manager Enhancements

New Member Pseudo Attribute - ContactID

What is changing:

ARCOS has created a new member level pseudo attribute called “ContactID”. This attribute will return the member’s contact ID in the ARCOS database. This will allow for easier searching of the member via the Employee Search feature and the API.

Who is involved:

All Crew Manager customers will receive this update.

What you need to do:

No further action is necessary to implement this change. If you wish to use this attribute, you will need to add it to the necessary view sets.

Platform Enhancements

Assign Multiple Security Groups to a User

What is changing:

ARCOS has added the ability to assign a user to multiple security groups. This can be done through the Employee Modify page, Employee Mass Modify page and the /employees API endpoint.

In the web application, the Security Group dropdown has been changed to a multi-select picker. Click and drag or ctrl+click to select multiple security groups.

Additional Notes

• For the employee's API, "securityGroups” must be passed as a separate element for the employee.
  • Prior to the change security group assignments were returned and sent as: “sec_group_id” within the attributes array 
    • 
  • After the change, security group assignments will be returned and sent as “securityGroups”
    • 
• The Grant Temporary Security Access feature acts as an “and” and adds the temporary assignment to the user’s current list of security groups. No security groups will be removed.
• Assigning a user to multiple security groups acts like an “and”. If one of the assigned security groups has access, then the user will have access to the feature.
• Wherever a user’s security group is currently displayed, the user’s security groups will now be displayed coma separated.

Who is involved:

All customers will receive this update.

What you need to do:

With the 24.50 release to QA, all customers will receive this update. This change will be deployed to production for all customers with the 25.10 production deploy on Thursday, March 6. You can request this change sooner by contacting ARCOS Support or Professional Services.

Users should verify with their IT teams that their integrations will not be affected by the API changes prior to requesting this enabled in production. Once enabled in production, it will require manual work by the customer before we can revert the change.