docs(access): add link to docs on organization page

!28 #39

docs/projects/django-template/user/access/index.md

@@ -6,7 +6,11 @@ template: project.html
 about: https://gitlab.com/nofusscomputing/infrastructure/configuration-management/django_app
 ---
 
+The Access module provides the multi-tenancy for this application. Tenancy is organized into organizations, which contain teams which contain users. As part of this module, application permission checking are also conducted. To view the details on how the permissions system works, please view the [application's API documentation](../../development/api/models/access_organization_permission_checking.md).
+
 
 ## Components
 
 - [Organization](./organization.md)
+
+- [Team](./team.md)

docs/projects/django-template/user/access/organization.md

@@ -6,14 +6,14 @@ template: project.html
 about: https://gitlab.com/nofusscomputing/infrastructure/configuration-management/django_app
 ---
 
-An organization is how multi-tenancy is conducted within this application.
+An organization is how multi-tenancy is conducted within this application. All data within the application is tied to an organization and only users whom are members of the organization with the correct permission can view that item within an organization.
+
+!!! warning
+    Any object within any organization that has been marked as `global`. Any user whom has the correct `view` permission will be able to see the global object. 
+    
+    _**Note:**: This does not include other items that may be attached to the global object that is itself not marked as global._
 
 
 ## Organization Manager
 
-An organization manager is to be viewed as the "owner" of an organization. With the exception of editing the organization itself, the manager can conduct **ALL** operations against an organization regardless of their permissions.
-
-
-## Teams
-
-A team is a way of grouping users and permissions.
+An organization manager is to be viewed as the "owner" of an organization. With the exception of editing the organization itself, the manager can conduct **ALL** operations against an organization regardless of their permissions. An orgnization manager does not need any permissions to add, change delete or view a `Team` or `Team User`. This also includes not requiring the `view` permission for an `Organization`.