This is an old revision of the document!
AGTEK Access as originally imagined did not have permissions associated with files and folders. If a user account existed for a company and is successfully authenticated, that user has permissions on all files and folders for that company. The intent was to keep AGTEK Access as simple as possible for the end user and avoid the complexity that permissions systems can introduce.
To make it more likely for bigger companies with branches to pool keys it's desirable to add some level of permissions to AGTEK Access. The goal still is to minimize complexity for the users. With that in mind, this solution should be implemented on the folder level with granularity provided by user access lists.
An incomplete list: