Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Customers can now opt in to an automated procedure that aims to lock inactive users. This makes sense to increase security, but also helps to save paid licenses, since all license assignments are removed from a user when it's locked. The default config of the feature will send emails twice a week to users which have not logged in for 90 days to any tool or the DevOps Portal. The email asks the user to simply log in to the DevOps Portal or any other tool to be regarded again as active. If this is not done, and the grace period of 10 days has passed, the user is locked.
For continuous operation of Portal API scripts, it's now possible to create and administer Technical Portal Users on the technical users page. Use with care, since these Portal Tech Users have the full power of Portal Admins and therefore could delete all projects and users! Like the Portal API itself, the feature is only enabled on request of the customer. In addition, Portal Tech Users can only call the API from well-defined IP addresses of the customer.
Improvements
Improved error messages when outdated or already used activation links are called. The presented information is balanced between the best possible user feedback and security requirements.
