Last modified by Xwiki VePa on 2024/02/07 07:37
Show last authors
1 {{layout}}
2 {{layout-section ac:type="single"}}
3 {{layout-cell}}
4 (% style="letter-spacing: 0.0px;" %)**Table of contents**
5
6 {{toc/}}
7
8 ----
9 {{/layout-cell}}
10 {{/layout-section}}
11
12 {{layout-section ac:type="single"}}
13 {{layout-cell}}
14 = (% style="font-size: 24.0px;letter-spacing: -0.01em;" %)**How to open the resource settings**(%%) =
15
16 To edit a resource, you have to click on the gear wheel in the toolbar of the resource. (% style="color: rgb(23,43,77);" %)This symbol is only visible to portal, provider and resource admins. (%%)Now a new window called "**//Edit Resource//**" opens with multiple tabs. Whenever you edit your resource be sure to click “**//Update//**” to save the changes you made. By just clicking the “**//Close//**” button your changes will not be saved.
17
18 [[image:attach:demo_ressources_scheduler.png]]
19
20 ----
21 {{/layout-cell}}
22 {{/layout-section}}
23
24 {{layout-section ac:type="single"}}
25 {{layout-cell}}
26 = **Visibility of resources** =
27
28 The visibility of your resources can be altered in the tab “//**Options**//” of the resource settings. (% style="letter-spacing: 0.0px;" %)The resources of your provider are by default only visible to users with access to your provider or direct access to the resource. Keep in mind, that users which can see are resource are not necessarily able to book it. The section "//**Access and use of resources**//" will give you more information on this topic.
29
30 (% style="letter-spacing: 0.0px;" %)[[image:attach:demo_options_visibility.png]]
31
32 == **Option 1: Access to provider (No additional settings)** ==
33
34 If the user has access to the provider, he will see all connected resources if no changes in the settings have been made. Keep in mind that this is the default setting with no tick in the resource visibility settings.
35
36 == **Option 2: Visibility set to “//Invisible//”** ==
37
38 If you tick “Invisible” in the resource visibility settings no one will see this resource. Even for admins of the resource it will be invisible in the scheduler and only be accessible via the tab ADMIN.RESOURCES. People with access to this resource will also not be able to see this resource.
39
40 == **Option 3: Visibility set to “//Only visible with direct/request access to resource//”** ==
41
42 The resource will only be visible to users with direct access (these users are listed and can be administered in the “**//Access//**” tab) or users, who are granted access to the resource via an active service request.
43
44 == **Option 4: Visibility set to “//Only visible with direct access to resource//”** ==
45
46 The resource will only be visible to users with direct access to the resource. These users are listed and can be administered in the “**//Access//**” tab.
47
48 == **Option 5: Visibility set to “//Public//”** ==
49
50 If this option is chosen, the resource can be seen by the public on the OpenIRIS website without login. But for users that are logged in, the resource is only seen in the scheduler if they do have provider access or any other direct access to the resource. Otherwise the resource is only visible under browse. The button “//**show form**//” can only be selected when the visibility is set to public. This means that the booking form or service request form will be publicly visible.
51
52 == **Option 6: “//Hide usage statistics//”** ==
53
54 By default, the usage statistics is visible for everyone with access to the resource as well as a distribution list with the email addresses of all users. This can be seen when opening the details of a resource. If this option is chosen, this tab is invisible for everybody. Admins can still see the user statistics in the tab ADMIN.STATISTICS and the distribution list of the resource in the scheduler with the white square.
55
56 [[image:attach:demo_details_usage.png]]
57
58 == **Option 7: No provider access** ==
59
60 If a user has no access to the provider but the access request is enabled in the provider settings by the provider administrator, then the user can send an access request to the provider. Once approved the user is able to see all resources.
61
62 ----
63 {{/layout-cell}}
64 {{/layout-section}}
65
66 {{layout-section ac:type="single"}}
67 {{layout-cell}}
68 = **Timeline/ Calendar visibility** =
69
70 The visibility of timeline and calendar can be altered in the tab “//**Options**//” of the resource settings. By default, the timeline and calendar of a resource are visible to any user.
71
72 [[image:attach:demo_options_visibility of timeline.png]]
73
74 1. **Hide if no access: **(% style="letter-spacing: 0.0px;" %)The timeline and calendar will not be shown to people who do not have access to this resource if this option is chosen.
75 1. **Anonymize bookings: **(% style="letter-spacing: 0.0px;" %)This option allows to anonymize bookings in timeline and calendar. Only for your own bookings the name will be shown. All other bookings are just shown by empty boxes. 
76 [[image:attach:demo_anonymized booking.png]](%%)
77 To anonymize bookings you can select between: "//if no access//" (people with no access will be shown an anonymized timeline), "//always//" (every user except the admins sees an anonymized timeline), "//if booking is from a different organization//" (booking will be anonymized if user belongs to a different organization) or "//if no access + if booking is from a different organization//" (combination of both).
78 \\
79 1. (% style="letter-spacing: 0.0px;" %)**Users cannot see the booking details of others: **If this option is enabled bookings details are not visible to other users. The choices of the dropdown menu are the same as for the anonymization of bookings.
80 1. (% style="letter-spacing: 0.0px;" %)**Show 12h by default: **With this setting the timeline will be shown in a 12 hours format instead of a 24 hours format by default. Users can change this manually for themself if preferred. Additionally the start time of the 12 hours can be set. The default start time is 8 am.
81
82 ----
83 {{/layout-cell}}
84 {{/layout-section}}
85
86 {{layout-section ac:type="single"}}
87 {{layout-cell}}
88 = **Access and use of resources** =
89
90 Users who see your resource do not necessarily have access to it. There are multiple options on how access can be granted and how users can use your resource.
91
92 == **Direct access** ==
93
94 The direct access of individual users can be granted in the “**//Access//**” tab of the resource settings. By clicking on the “**//Add user…//**” drop-down and either choose one of the proposed users or enter the email address of the user, that should be added. After selecting one, click on the “**//OK//**” button.
95
96 = [[image:attach:demo_resource direct access_add user.png]] =
97
98 There are also options to add new users, search for users from non-affiliated organizations and to bulk import users. This allows you to grant access to users who do not have an OpenIRIS account. It is also possible for users with no provider access to get direct access to a resource. Then this will be the only visible and accessible resource from your provider.
99
100 = [[image:attach:demo_resource direct access_new user.PNG]][[image:attach:demo_resource direct access_bulk import user.PNG]] =
101
102 You can grant access to whole groups, departments, organizations, projects and communities in the same way.
103
104 It is also possible to inherit the permissions from the provider access settings by ticking the button "**//inherit from provider access//**" in the access tab. When selected all access tabs are grayed out.
105
106 [[image:attach:demo_inherit access.PNG]]
107
108 [[image:attach:demo_inherit access_active.PNG]]
109
110 \\
111
112 == **Access request** ==
113
114 In the “//**Options**//” tab it is also possible to tick the button “//**Access request by users**//”. This enables users which do not have access to this resource to send you a request to access you resource. (% style="color: rgb(0,0,0);" %)How they can do this can be found [[here>>doc:openirisIO.Open IRIS.Open IRIS Documentation.User guide.Requests.WebHome||anchor="Access"]]. Additionally it is possible to optionally add a [[form >>doc:openirisIO.Open IRIS.Open IRIS Documentation.Admin guide.Form.WebHome]]to the access request.
115
116 = [[image:attach:demo_options_access request.png]] =
117
118 After a request was submitted you will get informed by email. In the end of the mail you will find links to directly approve or reject this request.
119
120 [[image:attach:demo_access request_admin mail.png]]
121
122 You can also answer requests in the ADMIN.INBOX by clicking on the gear wheel. There you can also edit all previous request and change their status.
123
124 [[image:attach:demo_edit access_admin inbox.png]]
125
126 Additionally, you can answer this request in OpenIRIS in the tab “**//Access//**”. You will find all requests marked in red. On the right you can either accept the request by clicking on the lock symbol or reject it by clicking on the arrow symbol. The user who send the request will automatically be informed.
127
128 [[image:attach:demo_access request_admin response.png]]
129
130 == **Booking approval** ==
131
132 When ticking the box “//**Booking approval**//” at the bottom of the “**//Options//**” tab, users can send a booking request each time they want to book your resource even, when they do not have access to. Every booking request needs to be approved by an admin. But once the users have a direct access to your resource the booking does not need approval anymore. You will be informed about every booking request via email. The user will be automatically informed when you approve or decline the booking request. Please keep in mind that the admins can also change parts of the booking prior to accepting it. A repeated booking only needs to be approved once by the admin. If the user changes an approved booking a new re-approval in needed.
133
134 [[image:attach:demo_booking approval.png]]
135
136 == **Administrate access of users** ==
137
138 All users who have access to the resource can be administered in the tab “**//Access//**”. By clicking on the symbol with the open lock you can disable the access of the user to this resource. The user will still remain in this list and can always be re-enabled to use the resource. By clicking on the x symbol you can remove this user completely from using your resource. The user will then no longer appear in the list. However, the user can (if the option is enabled) still send access requests for this resource in the future. (% style="color: rgb(193,199,208);" %)To read how an access request works click here.
139
140 [[image:attach:demo_administrate user access.png]]
141
142 == **Request based booking** ==
143
144 There is also the possibility to allow booking only after a request. This means that by default no one has access to your resource even when it is visible. However, a request to book this resource can be send via the corresponding service. If admins accept this request, the user will be able to book the resource for a defined period of time. When this period of time runs out the request can either be prolonged or left to run out.
145
146 To have this option you need to enable "//**Request based booking**//" in the "//**Options**//" tab. Please keep in mind, that users with direct access to your resource will not need a request to make bookings.
147
148 [[image:attach:demo_enable request based booking for resource.png]]
149
150 Additionally, a new service needs to be created over which the requests are inquired. In the following example the request based booking is enabled for a bioanalyzer.
151
152 [[image:attach:demo_create a service.png]]
153
154 This service needs some additional settings to function as a service request for one or multiple resources. First of all, the corresponding resources need to be added to the service. This can be done in the "//**Resources**//" tab. The number in brackets shows how many resources are already linked to this service. When clicking on "**//Select Resource(s)//**" all resources for whom you are an admin are showed. Now you can select and deselect as many as you want. But do not forget to click "//**Update**//" in the end.
155
156 [[image:attach:demo_add resources.png]]
157
158 Additionally, you can display the start and end date of this request in the "//**Options**//" tab. Then you can set the default duration of a request and when the request should be closed if no extension was made. In the "//**Settings**//" tab it is possible to enable remainder emails for the start or/and the end date.
159
160 [[image:attach:demo_options for service.png]][[image:attach:demo_service settings for reminder emails.png]]
161
162 Now everybody who has access to the service can send a request for your resource. If a request is send you will be informed by email. Now this user is visible in the ADMIN.INBOX (marked in red as the status is still pending). By clicking on the little triangle more options become visible. You can now make bookings for this user and change the settings and status for his request. If the status is changed, the user will be informed automatically by email.
163
164 [[image:attach:demo_admin inbox.png]]
165
166 If you want to get additional information from the users, you can add a form for the service in the "//**Form**//" tab. This form will then be shown to every user who wants to send a request. The request can only be send if all required fields are filled out. Please keep in mind that this does not change anything for the users who have already send a request. (% style="color: rgb(0,0,0);" %)To read more on how to [[create a form click here>>doc:openirisIO.Open IRIS.Open IRIS Documentation.Admin guide.Form.WebHome]].
167
168 ----
169 {{/layout-cell}}
170 {{/layout-section}}
171 {{/layout}}