TheocBase/Test

Inform all users about the steps they are involved in.

Click on the <img src="../images/cloud_delete_24x24.png" alt="" width="24" height="24" /> button to delete the cloud storage.

Click on the <strong>Yes</strong> button and confirm to delete the cloud data.

On synchronizing as <strong>administrator</strong> with another device after this time, a dialog appears with the message, that the cloud data has been deleted. The dialog needs to be confirmed with <strong>Yes</strong> or <strong>Continue</strong>, in order to discard the local data on that device and replace it by the cloud data. As a <strong>non-administrator</strong> these steps take place automatically.

In the next message box select <strong>Synchronize</strong> to upload the local TheocBase data to the cloud. If you click on <strong>Sign out</strong> you will be <a href="#disconnect_cloud_storage">disconnected from the cloud storage</a>.

Disconnect the Cloud Storage

Click on the <img src="../images/logout_24x24.png" alt="" width="24" height="24" /> button to disconnect the cloud storage.

Access control settings will be removed locally and the data in TheocBase will be cleared, if it was shared by someone else.

Settings - Access Control

Settings

Access Control

Getting Started

TheocBase uses role-based access control for users that have access to the shared data in the cloud. Roles provide a set of permissions. Thus a person assigned to a certain role is granted the set of permissions provided by that role.

By default, each user is automatically assigned to the basic <strong>Publisher</strong> role. The exception to this is the one person who shares the data file. That person is always assigned the <strong>Administrator</strong> role. It is also possible to assign the <strong>Administrator</strong> role to an additional user to assist with administrator functions.

The administrator’s role centers around maintaining and setting up the basic environment. This includes granting other users and himself any roles needed to accomplish the tasks related to that user’s assignments in the congregation.

Note:

The <strong>Administrator</strong> role does NOT inherently include all other permissions. This is in order to allow the owner of the cloud storage to work safely with the data files while limiting his access to only the necessary information. In case of a need, though, he can temporarily grant himself more roles/permissions to fix an issue.

The following list provides the available roles with their respective permissions:

<strong>Publisher:</strong> View and print midweek and weekend meeting schedule; view the congregation's territory; view special events

<strong>Elder:</strong> View congregation settings, list of public talks, songs and publishers