TheocBase/TheocBase
-
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.
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.
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.
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.
-
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
<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. -
<strong>Life and Ministry Meeting Chairman:</strong> View publishers, availabilities and midweek meeting settings; edit midweek meeting schedule; send reminders; print midweek meeting worksheets
<strong>
Life and Ministry Meeting Chairman:</strong>
View publishers, availabilities and midweek meeting settings; edit midweek meeting schedule; send reminders; print midweek meeting worksheets -
<strong>Life and Ministry Meeting Overseer:</strong> Edit publishers, availabilities, special events, midweek meeting schedule and settings; print assignment slips
<strong>
Life and Ministry Meeting Overseer:</strong>
Edit publishers, availabilities, special events, midweek meeting schedule and settings; print assignment slips -
Printing Tags - Weekend Meeting
Printing Tags - Weekend Meeting
Теги печати - встречи в выходные -
Printing Tags
Printing Tags
Теги печати -
Here is the list of printing tags along with their corresponding values. The tags may be available only at certain levels e.g.:
Here is the list of printing tags along with their corresponding values. The tags may be available only at certain levels e.g.:
Вот список тегов печати с соответствующими значениями. Теги могут быть доступны только на определенных уровнях, например: -
throughout the whole content of the template [1]
throughout the whole content of the template [1]
по всему содержанию шаблона [1] -
within the scope of a loop [2]
within the scope of a loop [2]
в рамках цикла [2] -
or even in a nested loop [3]
or even in a nested loop [3]
или даже во вложенном цикле [3] -
A loop has a start and an end tag. These are named accordingly (<code>*_START; *_END</code>) and have a description <span class="pt_loop_description">[between brackets]</span> in the <strong>Value</strong> column that mentions also the <strong>Scope</strong> of the tags that are available. If a printing tag returns a variable, then the value is described <var class="pt_variable_description">{between curly brackets}</var>; otherwise the mentioned text appears.
A loop has a start and an end tag. These are named accordingly (
<code>
*_START; *_END</code>
) and have a description<span class="pt_loop_description">
[between brackets]</span>
in the<strong>
Value</strong>
column that mentions also the<strong>
Scope</strong>
of the tags that are available. If a printing tag returns a variable, then the value is described<var class="pt_variable_description">
{between curly brackets}</var>
; otherwise the mentioned text appears.У цикла есть начальный и конечный теги. Они названы соответственно (<code>
*_START; *_END</code>
) и имеют описание<span class="pt_loop_description">
[в скобках]</span>
в столбце<strong>
Значение</strong>
, которое упоминает также<strong>
Область</strong>
доступных тегов. Если тег печати возвращает переменную, тогда значение описывается<var class="pt_variable_description">
{в фигурных скобках}</var>
; в противном случае появится упомянутый текст. -
Weekend Meeting
Weekend Meeting
Встреча на выходных -
Weekend Meeting Printing Tags
Weekend Meeting Printing Tags
Теги печати встречи в выходные -
Tag
Tag
Тег -
Value
Value
Значение -
Scope
Scope
Масштаб -
<!-- Printing tag: -->DATE<!-- Don't translate this. -->
<!-- Printing tag: -->
DATE<!-- Don't translate this. -->
<!-- Printing tag: -->
DATE<!-- Don't translate this. -->
-
{date}
{date}
{date}