access:trackwork_client_api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:trackwork_client_api [2009/09/25 00:54] mmatthews |
access:trackwork_client_api [2012/10/10 17:11] (current) |
||
|---|---|---|---|
| Line 78: | Line 78: | ||
| * Functions for monitoring/trouble shooting the Access Server | * Functions for monitoring/trouble shooting the Access Server | ||
| - | If we decide to allow customers to administrate their own users then I would break Admin API up as follows: | + | If we decide to allow customers to administrate their own users then I would break the Admin API up as follows: |
| - Admin API (customer access) | - Admin API (customer access) | ||
| * Functions for managing users | * Functions for managing users | ||
| Line 100: | Line 100: | ||
| === Authenticated with Admin Privelages === | === Authenticated with Admin Privelages === | ||
| - | This state occurs when an authenticated user has admin privelages. If we decide to allow customers to administrate their own users then this may further break down into two levels: Customer based admin and Agtek support level admin. If we decide to do this then I think we have two levels of API, Admin API (customer admin) and Root API (Agtek support). | + | This state occurs when an authenticated user has admin privelages. If we decide to allow customers to administrate their own users then this may further break down into two levels: Customer based admin and Agtek support level admin. If we decide to do this then I think we have two levels of API, Admin API (customer admin) and Support API (Agtek support). |
access/trackwork_client_api.1253840099.txt.gz · Last modified: 2012/10/10 17:11 (external edit)
Page Tools
