Issued to all components needing secure interactions on the platform which does reject privileged access if it is incorrect. The studio publisher has an application key registered to their account which must be present in the login for access to be granted. 

An authentication, routing and session mechanism required by the studio designer to maintain content in SVG repositories. It ensures that no direct logins are created by any workstation to offer inconvenience to parties trying to compromise an account. 

A security measure whereby a work stations identity is registered to the user account on the platform for secure usage of a SVG repository. This will be managed by the repository manager to co-ordinate the first login and select the trusted station from a list. 

Secure credentials of a username and password are required for standard authentication to permit a user to login to a repository and work on the content. The user can change their password and email address them self via my user in the repository portal. 

After a users successful login a signed secure tokens is used to identify a valid session between the Studio App and the repository. It is encrypted and is invalidated if tampered with, upon which the repository will then disable the account and blacklist the user. 

A status indicator specifying if a users influence is isolated to only being able to change what they create or if it is global and be able to also change what others create. This facilitates the scenario when it is important to limit a users influence in a repository. 

All activity on the platform is audited and accessible through search utilities in the Repository Portal and Studio Publisher app. A users work history can  be searched by date with ability to navigate to changed entities in the relevant designer to review changes. 

Intrusions are logged any time a failed login occurs or an attempt is made to access any views that the users role does not permit access to. If a hacking attempt is recognized the IP address and user could be blacklisted and refused further access in a session. 

An application used to test all repositories security mechanisms by emulating a scenario whereby a Studio applications code is decompiled and running in an integrated development environment with credentials to compromise an account or repository.