How a administrator user is different from read-write user in Aruba Central?

Question

Q: How a administrator user is different from read-write user in Aruba Central?
A: Aruba Central allows administrator to create multiple user of different access levels to help manage the system.  This access levels include:
read only
read/write
guest operator
NOTE: These access levels can be imposed on a specific "ap group" or a set of "ap groups" or all of them.
Therefore looking at the roles, many of the aruba central customers, had a question of how a administrator user is different from read-write user. 
Administrator is the only user who can move access points between groups. Read/Write user Do Not Have Permission to execute this action.

Answer 1

Hi,
I've managed to get what I needed by using a shift register + event structure as suggested by Adnan. However, I face another problem after implementing SR+event. I've attached two files, first the original program and second the updated program using SR + event. (it's only the jpg file as I've forgotten to save the labview program, will upload the program by tomorrow.
In the original program, I have an elapsed time that is able to run continuously when I run the program. In the updated program, my elapsed time don't seem to run continuously when I run the program (as shown by elapsed time indicator). I need the elapsed time to run continuously as a input to calculate my motor profile.
I suppose this is caused by the introduction of the event structure, will adding a case structure to wrap the event structure solve the problem or is there another way to get pass this. Appreciate if someone could drop me a pointer or two.
Thanks
Attachments:
Mar 16 - continuous elapsed time.png ‏12 KB
Mar 16 - elapsed time not continuous after introducing shift register + event structure.png ‏17 KB