From wiki.ginstr.com
Jump to: navigation, search
Line 4: Line 4:
  
 
==Introduction and general points==
 
==Introduction and general points==
'''Single sign-on (SSO)''' is a property of access control of multiple related, but independent software systems. With this property a user logs in with a single ID and password to gain access to a connected system or systems without using different usernames or passwords, or in some configurations seamlessly sign on at each system.
+
'''Single Sign-On (SSO)''' is a property of access control of multiple related, but independent software systems. With this property a user logs in with a single ID and password to gain access to a connected system or systems without using different usernames or passwords, or in some configurations seamlessly sign on at each system.
This means that single page is used to log in to multiple applications which are enabled / disabled for each user account by supervisor admin based on software modules ordered from ginstr.
 
This multiple log in is ensured with common ticket which is added as post-fix in browser address of each application. (example https://my.ginstr.com/?ticket= here goes ticket number generated by SSO server)
 
In browser application opens in different browser tab always so that SSO server tab stay opened and user can easily operate in both SSO server tab and in opened application tab.
 
  
ginstr SSO server is located on address https://sso.ginstr.com/
+
This means that a single page is used to log in to multiple applications which are enabled/disabled for each user account, depending on which software modules have been ordered from ginstr.
  
 +
This multiple log in is ensured with common ticket which is added as post-fix in browser address of each application (e.g. <code><nowiki>https://my.ginstr.com/?ticket=*ticket_number_generated_by_SSO_server*</nowiki></code>)
  
[[File:sso_log_in_page_items_explained.png|thumb|250px|none|SSO log in screen]]
+
Each application opens in a separate browser tab so that the SSO server tab remains open and user can easily operate in both the [[#SSO_lobby|SSO server tab]] and in each application tab simultaneously.
  
 +
ginstr SSO server is located at <code>https://sso.ginstr.com/</code>
  
 +
[[File:sso_login_screen.png|thumb|left|600px|SSO login screen at https://sso.ginstr.com/]]
 +
{|
 +
|
 +
|'''<u>Legend</u>'''
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">1</span></div>
 +
|'''[[#e-mail_field|e-mail field]]'''
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">2</span></div>
 +
|'''[[#password_field|password field]]'''
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">3</span></div>
 +
|[[#Signing_up_for_new_SSO_account|'''sign up!''' link]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">4</span></div>
 +
|[[#forgot_password|'''forgot password?''' link]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">5</span></div>
 +
|[[#login_button|'''log in''' button]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">6</span></div>
 +
|[[#FAQ|'''questions and answers (FAQ)''' link]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">7</span></div>
 +
|[[#Logging_in_with_Facebook_or_Google_account|'''facebook sign up''' button]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">8</span></div>
 +
|[[#Logging_in_with_Facebook_or_Google_account|'''Google sign up''' button]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">9</span></div>
 +
|'''[[#ginstr_Support_Chat|ginstr Support Chat]]'''
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">10</span></div>
 +
|[[#Language selection|'''Language selection''' drop down]]
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">11</span></div>
 +
|'''ginstr logo''' (linked to http://ginstr.com/)
 +
|-
 +
|<div style="display:inline-block;width:auto;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#ff8000"><span style="color:white;font-size:88%;font-weight:bold">12</span></div>
 +
|Info about current version of ginstr SSO server
 +
|-
 +
|
 +
|
 +
|}
  
In bottom right corner of SSO log in screen there is drop down with languages where user have possibility to choose language in which SSO content will be displayed ('''NOTE:''' Not all listed languages are supported yet. If user choose unsupported language then content will be displayed in English)
 
  
 +
----
  
[[File:language_drop_down.png|thumb|250px|none|drop down menu with languages]]
+
====e-mail field====
 +
:If you used an e-mail address to sign up, enter this e-mail address in the e-mail field. Before you can log in, you must confirm your registration by clicking on the link in the e-mail that you received after signing up (see [[#activation|activation]] for more details.
  
 +
====password field====
 +
:This field is for the password chosen during sign up associated with your ginstr iD email address entered above. If you have forgotten your password you can use the "[[#forgot_password?_button|forgot password?]]" button to assign a new password.
  
Below log in form on right side of log in form there is link '''"questions and answers (FAQ)"''' which when clicked opens page with frequently asked questions where user can find some help regarding registration process and other content needed for start of work with ginstr platform
+
[[File:register_form.png|thumb|250px|registration form to create new ginstr iD account]]
 +
====Signing up for new SSO account====
 +
:To register a new account on ginstr SSO, click on the ''''sign up!'''' link positioned above the e-mail field to display the form for registering a new ginstr iD (ginstr account).
  
 +
:The registration form consists of the following fields:
 +
:*e-mail (required field)
 +
:*password (required field)
 +
:*re-enter password (required field)
 +
:*first name (required field)
 +
:*last name (required field)
 +
:*mobile number (optional)
 +
:*company (optional)
 +
:*language (drop down)
  
[[File:position_of_faq_link.png|thumb|250px|none|position of FAQ link on log in screen]]
+
:'''NOTE:'''
 +
::Your ginstr account will be created in the language selected in the language drop down. Currently, not all listed languages are supported. If user selects an unsupported language then content will be displayed in English.
  
[[File:faq_page.png|thumb|250px|none|FAQ page]]
+
:The registration form also contains links to [[#FAQ|frequently asked questions]] and the [https://www.ginstr.com/privacy-protection/ ginstr Privacy Policy].
  
 +
[[File:mail_appearance.png|thumb|250px|appearance of ginstr iD activation e-mail]]
 +
:After filling all required fields and clicking the <div style="display:inline-block;width:160px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#66d9ff"><span style="color:#404040;font-size:88%;font-weight:bold">register</span></div> button, you will be taken to a page informing you that your account is now registered and that a confirmation e-mail has been sent to the e-mail account used for registration.
  
In case user doesn't find needed answer on FAQ page or in this manual then on right side of log in screen there is chat which when clicked opens chat window where user can chat directly with ginstr customer support.
+
=====Activation=====
 +
:An activation e-mail will be sent from address '''notifications@ginstr.com''' with the subject ''''ginstr iD activation''''. This e-mail contains a link "'''Activate your ginstr iD'''" which must be clicked to activate your account. Upon successful activation, you will be taken to a page confirming that your ginstr iD is activated and you can now log in with the newly created ginstr iD & password at <code>https://sso.ginstr.com/</code>.
  
 +
:'''NOTE:'''
 +
::In case you do do not receive the activation e-mail shortly after completing the registration form, please check your junk/spam folder
  
[[File:chat_position.png|thumb|250px|none|position of chat on SSO log in page]]
+
====login button====
 +
:After entering your ginstr iD email address & password, press the <div style="display:inline-block;width:160px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#66d9ff"><span style="color:#404040;font-size:88%;font-weight:bold">log in</span></div> button to proceed to the [[#SSO_lobby|SSO lobby]].
  
 +
[[File:faq_page.png|thumb|250px|questions and answers (FAQ) page]]
 +
====FAQ====
 +
:Below the password field on the right side there is a '''"questions and answers (FAQ)"''' link which, when clicked, opens a page with frequently asked questions regarding the registration process and other content relevant to starting work with the ginstr SSO platform.
  
If user already have Facebook or Google account then in this case below log in form on left side of log in form there are two buttons which allow user to log in to ginstr SSO with their existing Facebook or Google accounts. Once click on this buttons if not logged in to Facebook or Google user will be asked for authorization and if already logged in user will be asked to grant access to ginstr.
+
====Logging in with Facebook or Google account====
 +
:If you already have a Facebook or Google account then the two buttons below the <div style="display:inline-block;width:160px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#66d9ff"><span style="color:#404040;font-size:88%;font-weight:bold">log in</span></div> button allows you to log in to ginstr SSO with your existing Facebook or Google credentials. If already logged in to Facebook or Google, you will be asked to grant access to ginstr. If you are not already logged in to Facebook or Google, you will be asked for authorization.  
  
 +
====forgot password====
 +
:If you have forgotten your password you can use the "'''forgot password?'''" link to assign a new password. This link is located on right side of log in form under password field.
  
[[File:facebook_google_position.png|thumb|250px|none|position of Facebook and Google log in buttons on SSO log in page]]
+
:Once user enter screen for password reset there can enter e-mail used for registration and after click on reset password button e-mail with instructions will be sent to that e-mail address.
  
 +
[[File:language_drop_down.png|thumb|250px|Language selection drop down]]
 +
====ginstr Support Chat====
 +
:If you have a question which is not answered in the [[#FAQ|FAQ page]] or in this manual, clicking the ''''Chat now'''' button on the right side of log in screen opens a chat window where you can chat directly with ginstr customer support.
  
In case user forgot password there is link to screen for resetting password. Link is called "forgot password?" and is located on right side of log in form under password field.
+
====Language selection====
Once user enter screen for password reset there can enter e-mail used for registration and after click on reset password button e-mail with instructions will be sent to that e-mail address.
+
:In bottom right corner of SSO log in screen there is drop down selection which allows you to select the language in which SSO content will be displayed.
  
[[File:reset_pass_position.png|thumb|250px|none|position of link which opens page to reset password]]
+
:'''NOTE:'''
 +
::Currently, not all listed languages are supported. If an unsupported language is selected then content will be displayed in English.
  
 +
==SSO lobby==
 +
Once logged in to ginstr SSO, the default set of applications icons will be displayed in the SSO lobby.
  
To register new account on ginstr SSO user should click on "sign up!" link positioned on top right side of log in form above e-mail field
+
[[File:default_apps_lobby.png|thumb|250px|default applications icons in the SSO lobby]]
 +
These default applications are:
 +
:;ginstr home page: opens <code>https://www.ginstr.com/</code>
 +
:;[[ginstr web]]: opens [[ginstr web]] client which contains tables where the master data for ginstr applications is defined and where data sent from ginstr applications is stored
 +
:;OpenCellID: opens OpenCellID application
  
[[File:signup_position.png|thumb|250px|none|position of sign up link]]
+
Upon clicking on the [[ginstr web]] icon for the first time, you will be asked to accept "Conditions of Use for ginstr Applications". After accepting these conditions of use, they will not appear again on launching of [[ginstr web]] application.
  
==Signing up for new SSO account ==
+
:'''NOTE:'''
Once user click on sign up! link on log in page of ginstr SSO a page with form for registering new ginstr iD (ginstr account) will open.
+
::Even though your account is now activated, you will not be able to use [[ginstr web]] without first purchasing some ginstr subscription from the '''[https://shop.ginstr.com/produkt-kategorie/subscriptions/ ginstr shop]''' <code>error (1017) ginstr is disabled</code>
  
This form have following fields:
+
[[File:ginstr_lobby_name_topRH.png|thumb|250px|User name at top right-hand corner of the lobby]]
*e-mail (required field)
+
===SSO lobby menu===
*password (required field)
+
[[File:contact_form.png|thumb|250px|contact form appearance]]
*re-enter password (required field)
+
[[File:private_app_section.png|thumb|250px|configure private applications page]]
*first name (required field)
 
*last name (required field)
 
*mobile number (optional)
 
*company (optional)
 
  
Also there is drop down with languages. Account will be created in language which is selected in this drop down (if language not supported yet if will be created in English language)
+
Your user name is displayed at the top right corner of the SSO lobby screen when logged in. When you hover the mouse over this user name, a drop down menu opens.
There are also links that open page with frequently asked questions and page with privacy policy on ginstr web site.
 
  
[[File:register_form.png|thumb|250px|none|appearance of form for registering new ginstr iD]]
+
:Items in this menu are:
 +
:*[[#contact_form|contact form]]
 +
:*[[#questions_and_answers_(FAQ)|questions and answers (FAQ)]]
 +
:*[[#configure_private_applications|configure private applications]]
 +
:*[[#my_account|my account]]
 +
:*[[#conditions_of_use|conditions of use]]
 +
:*[[#imprint|imprint]]
 +
:*[[#privacy_policy|privacy policy]]
 +
:*[[#log_out|log out]]
  
 +
====contact form====
 +
:Opens page with contact form that enables user to contact ginstr support via e-mail
  
Once fill all required fields and click on "register" button user will be taken to page with info that account is registered and that confirmation e-mail is sent to e-mail account that was used for registration.
+
:In this form all fields are required to be filled.
e-mail will be sent from address notifications@ginstr.com and will be titled ginstr iD activation (please check spam folder in case e-mail not appears in inbox folder shortly)
 
and will contain link "Activate your ginstr iD" which when clicked will activate your account.
 
  
 +
====questions and answers (FAQ)====
  
[[File:mail_appearance.png|thumb|250px|none|appearance of ginstr iD activation e-mail]]
+
:Opens the [[#FAQ|frequently asked questions]] page
  
Clicking "Activate your ginstr iD" link will take you to page where it will be confirmed that ginstr iD is activated and which will enable user to log in with newly created ginstr iD on ginstr SSO log in page.
+
====configure private applications====
  
 +
:Displays private applications created by user. Private applications are only visible to their owner. Here you can view information on each private application and have the option to permanently remove each private application from the server.
  
==SSO lobby ==
+
====my account====
Once log in to ginstr SSO default set of applications icons will be displayed in SSO lobby.
 
This applications are:
 
  
*ginstr home page - opens https://www.ginstr.com/
+
:Opens the [[#My_account_page|my account]] page containing settings related to your user account. See <u>[[#My_account_page|here]]</u> for more information.
*ginstr web - opens ginstr web client which contains tables where master data for ginstr applications is defined and where data sent from ginstr applications is stored
 
*OpenCellID - opens OpenCellID application
 
  
 +
[[File:conditions_of_use.png|thumb|250px|conditions of use for ginstr applications]]
 +
====conditions of use====
  
[[File:default_apps_lobby.png|thumb|250px|none|default applications icons in SSO lobby]]
+
:When you hover your mouse over this menu item, a sub-menu appears. Clicking on the "ginstr web" sub-menu item displays the conditions of use for ginstr applications which you agreed to upon launching the ginstr web application from SSO lobby for the first time.
  
When click on ginstr web icon user will be asked to accept "Conditions of Use for ginstr Applications". This will be required to do only once and when user accept this conditions of use they will not appear again on launching of ginstr web application.<br>
+
====imprint====
'''NOTE:''' Even though account is now activated user will not be able to use ginstr web but will get error message "(1017) ginstr is disabled" until buy some ginstr subscription from ginstr shop https://shop.ginstr.com/produkt-kategorie/subscriptions/
 
  
In top right corner in SSO lobby there is user name displayed. When mouse over this user name drop down menu opens.<br>
+
:Click on this menu item to open the [https://www.ginstr.com/imprint/ imprint page] on the [https://www.ginstr.com/ ginstr web site]
  
 +
====privacy policy====
  
[[File:lobby_menu.png|thumb|250px|none|lobby menu position and appearance]]
+
:Click on this menu item to open the [https://www.ginstr.com/privacy-protection/ privacy protection page] on the [https://www.ginstr.com/ ginstr web site]
  
 +
====log out====
  
Items in this menu are:
+
:Click on this menu item to log out of ginstr SSO and return to theSSO log in screen
*contact form
 
*questions and answers (FAQ)
 
*configure private applications
 
*my account
 
*conditions of use
 
*imprint
 
*privacy policy
 
*log out
 
 
 
 
 
 
 
===contact form===
 
 
 
When click on this menu item then opens page with contact form that enables user to contact ginstr support via e-mail
 
 
 
[[File:contact_form.png|thumb|250px|none|contact form appearance]]
 
 
 
In this form all fields are required to be filled.
 
 
 
 
 
===questions and answers (FAQ)===
 
 
 
When click on this menu item then opens page with frequently asked questions
 
 
 
 
 
===configure private applications===
 
 
 
In this section are displayed private applications created by user. Private applications are only visible for user who is their owner. In this section user can see app info and have option to remove application from server.
 
 
 
[[File:private_app_section.png|thumb|250px|none|configure private applications page]]
 
 
 
 
 
===my account===
 
 
 
When click on this menu item opens page for settings related to account. This page will be described in details later
 
 
 
[[File:my_account.png|thumb|250px|none|my account page]]
 
 
 
 
 
===conditions of use===
 
 
 
When mouse over this menu item then sub menu item ginstr web appears. When click on that ginstr web sub menu item then page opens with displayed conditions of use for ginstr applications (same conditions of use which are displayed on first start of ginstr web application from SSO lobby)
 
 
 
[[File:conditions_of_use.png|thumb|250px|none|conditions of use for ginstr applications]]
 
 
 
 
 
===imprint===
 
 
 
When click on this menu item opens imprint page on ginstr web site https://www.ginstr.com/imprint/
 
 
 
 
 
===privacy policy===
 
 
 
When click on this menu item opens the privacy protection page on ginstr web site https://www.ginstr.com/privacy-protection/
 
 
 
 
 
===log out===
 
 
 
When click on this menu item then user gets logged out and return to SSO log in screen
 
  
  
 
==My account page==
 
==My account page==
 
+
[[File:my_account.png|thumb|250px|my account page]]
 
This page contains multiple sections:
 
This page contains multiple sections:
 
+
*[[#my_account|my account]]
*my account
+
**[[#general|general]]
**general
+
**[[#hide/show_content|hide/show content]]
**hide/show content
+
*[[#subaccounts|subaccounts]]
*subaccounts
+
*[[#roles|roles]]
*roles
 
 
 
[[File:my_account_details.png|thumb|250px|none|my account page structure]]
 
  
 
===my account===
 
===my account===
  
This section contains two sub sections: '''general''' and '''hide/show content'''
+
This section contains two sub-sections: '''[[#general|general]]''' and '''[[#hide/show_content|hide/show content]]'''
  
 
====general====
 
====general====
  
In this section are displayed all details related to account and here this details can be modified
+
This section displays all details related to your user account, some of which are editable.
 
 
[[File:general_details.png|thumb|250px|none|general section]]
 
 
 
Following items are present in general section:
 
 
 
*account
 
*role
 
*account status
 
*language
 
*e-mail
 
*password
 
*re-enter password
 
*NFC
 
*first name
 
*last name
 
*mobile number
 
*company (optional)
 
*disable chat support
 
*delete all data of all tables in this account older than (days)
 
*maximum number of rows that can be displayed in each table
 
 
 
 
 
 
 
'''account'''
 
 
 
Here is displayed username. This item is not editable
 
 
 
 
 
 
 
'''role'''
 
 
 
Here is displayed SSO role of account. This item is not editable
 
 
 
 
 
'''account status'''
 
 
 
Here is displayed status of account (active, suspended, deleted). This item is not editable
 
 
 
 
 
'''language'''
 
 
 
Here user can choose language in which SSO content will be displayed. Currently supported languages are English, German, Spanish, French, Hebrew and Arabic.
 
After language is selected in drop down user should click on "Apply" button at the end of general section in order to apply change of language
 
 
 
 
 
'''e-mail'''
 
 
 
Here user can enter personal or company e-mail.
 
 
 
 
 
'''password and re-enter password'''
 
 
 
These two fields are used to change current password. In order to change password user must enter new password in both password and re-enter password fields and after that click on "Apply" button at the end of general section. New password must contain at least one digit, one uppercase letter and not less than 8 symbols.
 
 
 
 
 
'''NFC'''
 
 
 
In this filed user can enter NFC tag id which will be then used for this user to log in to ginstr apps on Android devices by scanning that NFC tag.
 
 
 
 
 
'''first name and last name'''
 
 
 
In these fields user can modify first and last name which were entered on account creation.
 
 
 
 
 
'''mobile number'''
 
 
 
In this field user can enter private or company mobile number
 
 
 
  
'''company (optional)'''
+
The '''general''' section consists of the following items:
  
In this field user can enter name of company
+
:;account: Your ginstr iD user name is displayed here. This item is not editable
  
 +
:;role:The SSO role of your account is displayed here. This item is not editable
  
'''disable chat support'''
+
:;account status: The status of your account (active, suspended, deleted) is displayed here. This item is not editable
  
By checking this checkbox user will disable support chat and chat window will not be displayed in both SSO and ginstr web
+
:;language: Allows you to select the language in which SSO content will be displayed. Currently supported languages are English, German, Spanish, French, Hebrew and Arabic.
 +
::After selecting your preferred display language in the drop down, click the <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">apply</span></div> button at the end of general section to apply the language change.
  
 +
:;e-mail: In this field you can enter your personal or company e-mail.
  
'''delete all data of all tables in this account older than (days)'''
+
:;password and re-enter password: These two fields are used to change the current password. In order to change your password, you must enter the same new password in both password and re-enter password fields before clicking on the <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">apply</span></div> button at the end of general section.
 +
:The new password must contain at least one number, one uppercase letter and not less than 8 characters.
  
In this field user can define for how long data in all tables of all applications enabled for that account will be kept. Default value is 0 which means that data will be kept in tables forever. Value must be positive number. Maximal value is 999. After set desired value user must click on "Apply" button at the end of general section in order to apply changes.
+
:;NFC: In this field you can enter an [[NFC#NFC_Tags|NFC tag]] id. This allows you to log in to ginstr apps by scanning this [[NFC#NFC_Tags|NFC tag]] on Android devices with built-in [[NFC]] technology.
  
 +
:;first name and last name: In these fields you can modify first and last name which were entered on account creation.
  
'''maximum number of rows that can be displayed in each table'''
+
:;mobile number: In this field you can enter your personal or company mobile number.
  
Here user can define how much rows can be displayed in table before "filter by record creation date" appears in table. Once defined number of records is reached in some table then records in table will be grouped based on record creation date. This number of records is defined on browser and server level.
+
:;company (optional): In this field you can enter the name of your company.
  
 +
:;disable chat support: This checkbox disables support chat so that the chat window will no longer be displayed in either SSO or [[ginstr web]].
  
 +
:;delete all data of all tables in this account older than (days): In this field you can define how long the data in all tables of all applications enabled for your account will be kept.
 +
::Default value is 0 which means that data will be kept in tables forever.
 +
::Value must be positive number up to a maximum of 999 days.
 +
::After entering the desired value, click the <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">apply</span></div> button at the end of general section to apply the change.
  
 +
:;maximum number of rows that can be displayed in each table: Here you can define how many rows can be displayed in each [[ginstr web]] table before "filter by record creation date" appears in table. Once the defined number of records is reached in a table, the records in the table will be grouped based on record creation date. This number of records is defined on browser and server level.
  
 
====hide/show content====
 
====hide/show content====
 +
[[File:hideshow_section.png|thumb|250px|hide/show content section]]
 +
This section consists of a list of application tables with option to change permissions on each table and section where user can assign or unassign records that exist in table.
  
 +
The '''hide/show content''' section consists of the following items:
  
In this section is displayed list of applications, list of application tables with option to change permissions on those tables and section where user can assign or unassign records that exist in table. Also in this section user can set amount of days after which data will be deleted from tables on app and table level.
+
;list of ginstr applications: Here you will be shown a list of names of all ginstr applications which are enabled for your account.
  
 +
;list of tables of selected ginstr application: When you click on one or more application name in "list of ginstr applications", then all tables of the selected application(s) are displayed in "list of tables of selected ginstr application". For each table you can set the following permissions : create, read, update and delete (CRUD permissions). Here you have option to either enable or disable each permission for certain table by clicking each permission link. You can also select a table and then click on the "'''activate all'''" link above the list of tables to activate all permissions on the selected table.
 +
:If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web
  
[[File:hideshow_section.png|thumb|250px|none|hide/show content section]]
+
;list of records in selected table: When user select some table in "list of tables of selected ginstr application" part then "list of records in selected table" part appears with option to assign/unassign existing records in table.
 +
:When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">apply</span></div> button above the ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web .
  
 +
;interface for defining how much days to keep records in tables on application and table level: Above "list of tables of selected ginstr application" part and "list of records in selected table" part there are fields where user can define how long data in all app tables or in single app table will be kept.
  
Following parts exist in this section:
+
:This feature exists on 3 levels
 
+
:#all applications level (which exist in general section and is described there)
*list of ginstr applications
+
:#single application level - this field exist above "list of tables of selected ginstr application" part and when some number of days is defined there data in all tables of that app will be kept for that number of days and after that deleted
*list of tables of selected ginstr application
+
:#single table level - this field exist above "list of records in selected table" part and when some number of days is defined there data in that particular table will be kept for that number of days and after that deleted.  
*list of records in selected table
 
*interface for defining how much days to keep records in tables on application and table level
 
 
 
 
 
'''list of ginstr applications'''
 
 
 
In this part are displayed names of all ginstr applications which are enabled for that account
 
 
 
'''list of tables of selected ginstr application'''
 
 
 
When user click on some application name in "list of ginstr applications" part then all tables of selected application are displayed in "list of tables of selected ginstr application". For each table there are displayed following permissions : create, read, update and delete (CRUD permissions). Here user have option that by clicking on link with name of some permission either enable or disable that permission for certain table. Also user have option to select table and then click on "activate all" link above list of table and activate all permissions on selected tables.
 
If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web
 
 
 
'''list of records in selected table'''
 
 
 
When user select some table in "list of tables of selected ginstr application" part then "list of records in selected table" part appears with option to assign/unassign existing records in table.
 
When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on "apply" button above ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web .
 
 
 
'''interface for defining how much days to keep records in tables on application and table level'''
 
 
 
Above "list of tables of selected ginstr application" part and "list of records in selected table" part there are fields where user can define how long data in all app tables or in single app table will be kept. This feature exists on 3 levels <br>1. all applications level (which exist in general section and is described there)<br> 2. single application level - this field exist above "list of tables of selected ginstr application" part and when some number of days is defined there data in all tables of that app will be kept for that number of days and after that deleted<br> 3. single table level - this field exist above "list of records in selected table" part and when some number of days is defined there data in that particular table will be kept for that number of days and after that deleted.  
 
<br> General rule is: If define amount of days on level 1 then same amount of days will be applied on levels 2 and 3 for all apps. If define amount of days for some app on level 2 then same amount of days will be applied on level 3 for all tables of that app and for all other apps (and those apps tables) will be still applied amount of days defined on level 1. If define amount of days for some table on level 3 then this amount will be applied for that table only and all other tables of that application will have amount of days defined on level 2 of that application .
 
 
 
  
 +
:'''General rule:''' If define amount of days on level 1 then same amount of days will be applied on levels 2 and 3 for all apps. If define amount of days for some app on level 2 then same amount of days will be applied on level 3 for all tables of that app and for all other apps (and those apps tables) will be still applied amount of days defined on level 1. If define amount of days for some table on level 3 then this amount will be applied for that table only and all other tables of that application will have amount of days defined on level 2 of that application .
  
 
====subaccounts====
 
====subaccounts====
 +
[[File:subaccount_section.png|thumb|250px|subaccounts section]]
 +
In this section a main account user can create subaccounts. Amount of subaccounts which can be created by the main user is defined based on ginstr subscription. Main account is also called company account which means that, for example if a company has 10 workers which will be using application they will need to create 10 subaccounts on their main (company) account for each worker that needs to log in to application. The main account is used as an administrator for subaccounts created by that main account and can choose which applications subaccount can use and which permission the subaccount will have for each tables. The main account user can also delete subaccount created by that main account user.
  
In this section main account user can create subaccounts. Amount of subaccounts which can be created by main user is defined based on ginstr subscription. Main account is also called company account which means that for example if company have 10 workers which will be using application they will need to create 10 subaccounts on their main (company) account for each worker which will need to log in to application. Main account is like administrator for subaccounts created by that main account and can choose which applications subaccount can use and which permission will subaccount have on tables. Main account user can also delete subaccount created by that main account user.
+
The '''subaccounts''' section consists of the following items:
 
 
[[File:subaccount_section.png|thumb|250px|none|subaccounts section]]
 
 
 
 
 
This section contains of following parts:
 
  
 
*interface to add new subaccount and list of existing subaccount
 
*interface to add new subaccount and list of existing subaccount
Line 326: Line 272:
  
  
'''interface to add new subaccount and list of existing subaccount'''
+
;interface to add new subaccount and list of existing subaccount: When user click on "add subaccount" button on top of this section then interface will open where used can enter required data to create new subaccount.
 +
:*In ''''e-mail'''' field user should define e-mail which will be used as username of new subaccount.
 +
:*In ''''password'''' field user should define password which will be used by new subaccount for logging in. Under this field there is a checkbox labelled "show password" which, when checked will display the password in plain text.
 +
:*In ''''NFC'''' field user can define the [[NFC#NFC_Tags|NFC tag]] id which can be used by that new subaccount to log in to ginstr launcher and ginstr apps.
 +
:*In ''''role'''' drop down user can select some of roles which can be created by user and will be described in next section.
 +
:*In ''''applications'''' drop down user can select which applications will be enabled for subaccount
 +
:*In ''''access status'''' drop down user can select between active and suspended status. User can create unlimited number of subaccounts with suspended status but only that much subaccounts with active status as have allowed by ginstr subscription. Only active subaccounts will be possible to use ginstr web and ginstr apps.
 +
:*In ''''idle timeout (hh:mm)'''' field user can define amount of time after which if inactive subaccount will be logged out. Value should be set in range 00:20-24:00
 +
:*The'''''creating subaccounts allowed''''' checkbox, if checked, allows subaccount to create its own subaccounts <u>(This option is not yet supported)</u>
 +
:*''''user can use ginstr apps'''' and ''''user can use ginstr backend'''' checkboxes allow the main account to define whether or not each subaccount will be able to use ginstr web and/or ginstr apps.
 +
:Once all data is filled and the <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">add</span></div> button is clicked, the newly created subaccount appears in this section.
 +
:In the list of existing subaccounts main user have option in the list to click on show settings link which opens interface to edit existing subaccount or can click on trash can icon which will delete existing subaccount
  
When user click on "add subaccount" button on top of this section then interface will open where used can enter required data to create new subaccount. <br>In e-mail filed user should define e-mail which will be used as username of new subaccount. <br>In password field user should define password which will be used by new subaccount for logging in. Under this field there is checkbox "show password" which when checked will display password in text format.<br> In NFC field user can define NFC tag id which can be used by that new subaccount to log in to ginstr launcher and ginstr apps.<br>In role drop down user can select some of roles which can be created by user and will be described in next section. <br>In applications drop down user can select which applications will be enabled for subaccount<br>In access status drop down user can select between active and suspended status. User can create unlimited number of subaccounts with suspended status but only that much subaccounts with active status as have allowed by ginstr subscription. Only active subaccounts will be possible to use ginstr web and ginstr apps.<br>In idle timeout (hh:mm) field user can define amount of time after which if inactive subaccount will be logged out. Value should be set in range 00:20-24:00<br>creating subaccounts allowed checkbox if checked allows subaccount to create its own subaccounts. This option is not yet supported<br>user can use ginstr apps and user can use ginstr backend checkboxes allow main account to define if subaccount will be able to use ginstr web and/or ginstr apps.<br>Once all data filled when click on add button newly created subaccount appears in this section.<br>In list of existing subaccounts main user have option in list to click on show settings link which opens interface to edit existing subaccount or can click on trash can icon which will delete existing subaccount
+
;list of applications enabled for selected subaccount: This section displays the names of all ginstr applications which are enabled for that subaccount
 
 
'''list of applications enabled for selected subaccount'''
 
 
 
In this part are displayed names of all ginstr applications which are enabled for that subaccount
 
 
 
'''list of tables for selected applications'''
 
 
 
This part is same as described in hide/show content section.<br>
 
When user click on some application name in "list of ginstr applications" part then all tables of selected application are displayed in "list of tables of selected ginstr application". For each table there are displayed following permissions : create, read, update and delete (CRUD permissions). Here user have option that by clicking on link with name of some permission either enable or disable that permission for certain table. Also user have option to select table and then click on "activate all" link above list of table and activate all permissions on selected tables.
 
If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web<br> Main difference is that in hide/show content section tables are created with enabled permissions and in subaccount section tables are created without permissions so that main user can define permissions on tables for subaccount. <br> Both main account and subaccount are using same tables of applications so there are no two set of tables but only different permissions on same tables.
 
 
 
'''list of records in selected table'''
 
 
 
This part is same as described in hide/show content section.<br>
 
When user select some table in "list of tables of selected ginstr application" part then "list of records in selected table" part appears with option to assign/unassign existing records in table.
 
When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on "apply" button above ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web .<br> Since same tables are used for both main account and subaccount records created by main account and all existing subaccounts of that main account will be displayed in this section but it can be defined per each subaccount here which records will be displayed in table for that particular subaccount
 
  
 +
;list of tables for selected applications:This part is as described in [[#hide/show_content|hide/show content section]].
 +
:When user click on some application name in "list of ginstr applications" part then all tables of selected application are displayed in "list of tables of selected ginstr application". For each table there are four permissions displayed: create, read, update and delete (CRUD permissions). Here user have option that by clicking on link with name of some permission either enable or disable that permission for certain table. Also user have option to select table and then click on "activate all" link above the list of tables and activate all permissions on selected tables.
 +
:If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web
 +
:Main difference is that in [[#hide/show_content|hide/show content section]] tables are created with enabled permissions and in subaccount section tables are created without permissions so that main user can define permissions on tables for subaccount.
 +
:Both main account and subaccount are using same tables of applications so there are no two set of tables but only different permissions on same tables.
  
 +
;list of records in selected table:This part is same as described in [[#hide/show_content|hide/show content section]].
 +
:When user select some table in "list of tables of selected ginstr application" part then "list of records in selected table" part appears with option to assign/unassign existing records in table.
 +
:When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">apply</span></div> button, the ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in [[ginstr web]].
 +
:Since same tables are used for both main account and subaccount records created by main account and all existing subaccounts of that main account will be displayed in this section but it can be defined per each subaccount here which records will be displayed in table for that particular subaccount
  
 
====roles====
 
====roles====
 +
[[File:roles_section.png|thumb|250px|roles section]]
 +
In this section you can define different roles that can be assigned for that main user's subaccounts. Roles are templates of permissions and records assignments for apps and if role is assigned to some subaccount then tables permissions and records assignments defined in that role for certain app will be applied on that subaccount for that app if that app is enabled for that subaccount in subaccounts section.
 +
Once role is created it can be assigned to each subaccount (new or existing) in interface for adding/editing subaccounts. When in subaccount section in from some subaccount select role in roles drop down and save changes after that when click on that subaccount applications assigned to that subaccount will not appear on right side in "list of applications enabled for selected subaccount" part. This means that permissions and records assignments defined by role are now applied on that subaccount.
  
In this section user can define different roles that can be assigned for that main user's subaccounts. Roles are templates of permissions and records assignments for apps and if role is assigned to some subaccount then tables permissions and records assignments defined in that role for certain app will be applied on that subaccount for that app if that app is enabled for that subaccount in subaccounts section.<br> Once role is created it can be assigned to each subaccount (new or existing) in interface for adding/editing subaccounts. When in subaccount section in fro some subaccount select role in roles drop down and save changes after that when click on that subaccount applications assigned to that subaccount will not appear on right side in "list of applications enabled for selected subaccount" part. This means that permissions and records assignments defined by role are now applied on that subaccount.
+
The '''roles''' section consists of the following items:
 
 
[[File:roles_section.png|thumb|250px|none|roles section]]
 
 
 
 
 
This section contains of following parts:
 
 
 
*interface to add new role and list of existing roles
 
*list of applications enabled for main account
 
*list of tables for selected applications
 
*list of records in selected table
 
 
 
 
 
'''interface to add new role and list of existing roles'''
 
 
 
When user click on add role button interface for adding new role opens with enter role name and enter description fields. Once user fills this fields and click on add button new role is created and is now displayed in list of existing roles. Existing role have link show settings which when clicked enables user to edit name and description of role, delete icon which when clicked enables user to delete existing row and there is displayed names and total number of subaccounts assigned to that role.
 
 
 
 
 
'''list of applications enabled for main account'''
 
 
 
When User clicks on existing role then on right side appears list of all applications enabled for main account
 
 
 
 
 
'''list of tables for selected applications'''
 
  
When user click on some of applications from list in list of applications enabled for main account part then in list of tables for selected applications appear all tables of that selected app. Tables are displayed without enabled permissions so that user can define permissions.
+
;interface to add new role and list of existing roles: When you click on the ''''add role'''' button, the interface for adding a new role opens with ''''enter role name'''' and ''''enter description'''' fields. Once you fill these fields and click on the <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">add</span></div> button, the new role is created and displayed in the list of existing roles.
For each table there are displayed following permissions : create, read, update and delete (CRUD permissions). Here user have option that by clicking on link with name of some permission either enable or disable that permission for certain table. Also user have option to select table and then click on "activate all" link above list of table and activate all permissions on selected tables.
+
:Existing role has an option to ''''show settings'''' which, when clicked enables you to edit the name and description of a role,a ''''delete'''' button, which when clicked enables you to delete existing row and there are names displayed and total number of subaccounts assigned to that role.
If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web.<br> Permissions defined here will be applied on subaccount if that role is assigned to subaccount and it will override permissions defined directly on subaccount in subaccounts section
 
  
 +
;list of applications enabled for main account: When you click on existing role then on right side appears list of all applications enabled for main account
  
'''list of records in selected table'''
+
;list of tables for selected applications: When user click on some of applications from the list of applications enabled for main account part then in the list of tables for selected applications appear all tables of that selected app. Tables are displayed without enabled permissions so that user can define permissions.
 +
:For each table there are displayed following permissions : <code>create</code>, <code>read</code>, <code>update</code> and <code>delete</code> (CRUD permissions). By clicking on the link with name of some permission, you can either enable or disable that permission for certain table.
 +
:There is also the option to select a table and then click on ''''activate all'''' link above the the list of tables and activate all permissions on selected tables.
 +
::If <code>create</code> permission is enabled on a table, this means that user will be able to create new records in that table.
 +
::If <code>read</code> permission is enabled on a table, this means that user will be able to see that table in [[ginstr web]].
 +
::If <code>update</code> permission is enabled on a table, this means that user will be able to modify existing records in table.
 +
::If <code>delete</code> permission is enabled on a table, this means that user will be able to delete records from that table in [[ginstr web]].
 +
:Permissions defined here will be applied on subaccount if that role is assigned to subaccount and it will override permissions defined directly on subaccount in subaccounts section
  
When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on "apply" button above ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web.<br> Assignments of records defined here will be applied on subaccount if that role is assigned to subaccount and it will override assignments of records defined directly on subaccount in subaccounts section
+
;list of records in selected table: When records are added to a table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user clicks on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user clicks on the <div style="display:inline-block;width:60px;height:auto;text-align:center;padding:0px 4px;vertical-align:middle;-moz-border-radius:3px;-webkit-border-radius:3px;border-radius:3px;background-color:#33CCFF"><span style="color:white;font-size:88%;font-weight:bold">apply</span></div> button above the ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in [[ginstr web]].
 +
:Assignments of records defined here will be applied on subaccount if that role is assigned to subaccount and it will override assignments of records defined directly on subaccount in subaccounts section

Revision as of 00:53, 4 November 2016

SSO Common Content

Introduction and general points

Single Sign-On (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in with a single ID and password to gain access to a connected system or systems without using different usernames or passwords, or in some configurations seamlessly sign on at each system.

This means that a single page is used to log in to multiple applications which are enabled/disabled for each user account, depending on which software modules have been ordered from ginstr.

This multiple log in is ensured with common ticket which is added as post-fix in browser address of each application (e.g. https://my.ginstr.com/?ticket=*ticket_number_generated_by_SSO_server*)

Each application opens in a separate browser tab so that the SSO server tab remains open and user can easily operate in both the SSO server tab and in each application tab simultaneously.

ginstr SSO server is located at https://sso.ginstr.com/

SSO login screen at https://sso.ginstr.com/
Legend
1
e-mail field
2
password field
3
sign up! link
4
forgot password? link
5
log in button
6
questions and answers (FAQ) link
7
facebook sign up button
8
Google sign up button
9
ginstr Support Chat
10
Language selection drop down
11
ginstr logo (linked to http://ginstr.com/)
12
Info about current version of ginstr SSO server



e-mail field

If you used an e-mail address to sign up, enter this e-mail address in the e-mail field. Before you can log in, you must confirm your registration by clicking on the link in the e-mail that you received after signing up (see activation for more details.

password field

This field is for the password chosen during sign up associated with your ginstr iD email address entered above. If you have forgotten your password you can use the "forgot password?" button to assign a new password.
registration form to create new ginstr iD account

Signing up for new SSO account

To register a new account on ginstr SSO, click on the 'sign up!' link positioned above the e-mail field to display the form for registering a new ginstr iD (ginstr account).
The registration form consists of the following fields:
  • e-mail (required field)
  • password (required field)
  • re-enter password (required field)
  • first name (required field)
  • last name (required field)
  • mobile number (optional)
  • company (optional)
  • language (drop down)
NOTE:
Your ginstr account will be created in the language selected in the language drop down. Currently, not all listed languages are supported. If user selects an unsupported language then content will be displayed in English.
The registration form also contains links to frequently asked questions and the ginstr Privacy Policy.
appearance of ginstr iD activation e-mail
After filling all required fields and clicking the
register
button, you will be taken to a page informing you that your account is now registered and that a confirmation e-mail has been sent to the e-mail account used for registration.
Activation
An activation e-mail will be sent from address notifications@ginstr.com with the subject 'ginstr iD activation'. This e-mail contains a link "Activate your ginstr iD" which must be clicked to activate your account. Upon successful activation, you will be taken to a page confirming that your ginstr iD is activated and you can now log in with the newly created ginstr iD & password at https://sso.ginstr.com/.
NOTE:
In case you do do not receive the activation e-mail shortly after completing the registration form, please check your junk/spam folder

login button

After entering your ginstr iD email address & password, press the
log in
button to proceed to the SSO lobby.
questions and answers (FAQ) page

FAQ

Below the password field on the right side there is a "questions and answers (FAQ)" link which, when clicked, opens a page with frequently asked questions regarding the registration process and other content relevant to starting work with the ginstr SSO platform.

Logging in with Facebook or Google account

If you already have a Facebook or Google account then the two buttons below the
log in
button allows you to log in to ginstr SSO with your existing Facebook or Google credentials. If already logged in to Facebook or Google, you will be asked to grant access to ginstr. If you are not already logged in to Facebook or Google, you will be asked for authorization.

forgot password

If you have forgotten your password you can use the "forgot password?" link to assign a new password. This link is located on right side of log in form under password field.
Once user enter screen for password reset there can enter e-mail used for registration and after click on reset password button e-mail with instructions will be sent to that e-mail address.
Language selection drop down

ginstr Support Chat

If you have a question which is not answered in the FAQ page or in this manual, clicking the 'Chat now' button on the right side of log in screen opens a chat window where you can chat directly with ginstr customer support.

Language selection

In bottom right corner of SSO log in screen there is drop down selection which allows you to select the language in which SSO content will be displayed.
NOTE:
Currently, not all listed languages are supported. If an unsupported language is selected then content will be displayed in English.

SSO lobby

Once logged in to ginstr SSO, the default set of applications icons will be displayed in the SSO lobby.

default applications icons in the SSO lobby

These default applications are:

ginstr home page
opens https://www.ginstr.com/
ginstr web
opens ginstr web client which contains tables where the master data for ginstr applications is defined and where data sent from ginstr applications is stored
OpenCellID
opens OpenCellID application

Upon clicking on the ginstr web icon for the first time, you will be asked to accept "Conditions of Use for ginstr Applications". After accepting these conditions of use, they will not appear again on launching of ginstr web application.

NOTE:
Even though your account is now activated, you will not be able to use ginstr web without first purchasing some ginstr subscription from the ginstr shop error (1017) ginstr is disabled
User name at top right-hand corner of the lobby

SSO lobby menu

contact form appearance
configure private applications page

Your user name is displayed at the top right corner of the SSO lobby screen when logged in. When you hover the mouse over this user name, a drop down menu opens.

Items in this menu are:

contact form

Opens page with contact form that enables user to contact ginstr support via e-mail
In this form all fields are required to be filled.

questions and answers (FAQ)

Opens the frequently asked questions page

configure private applications

Displays private applications created by user. Private applications are only visible to their owner. Here you can view information on each private application and have the option to permanently remove each private application from the server.

my account

Opens the my account page containing settings related to your user account. See here for more information.
conditions of use for ginstr applications

conditions of use

When you hover your mouse over this menu item, a sub-menu appears. Clicking on the "ginstr web" sub-menu item displays the conditions of use for ginstr applications which you agreed to upon launching the ginstr web application from SSO lobby for the first time.

imprint

Click on this menu item to open the imprint page on the ginstr web site

privacy policy

Click on this menu item to open the privacy protection page on the ginstr web site

log out

Click on this menu item to log out of ginstr SSO and return to theSSO log in screen


My account page

my account page

This page contains multiple sections:

my account

This section contains two sub-sections: general and hide/show content

general

This section displays all details related to your user account, some of which are editable.

The general section consists of the following items:

account
Your ginstr iD user name is displayed here. This item is not editable
role
The SSO role of your account is displayed here. This item is not editable
account status
The status of your account (active, suspended, deleted) is displayed here. This item is not editable
language
Allows you to select the language in which SSO content will be displayed. Currently supported languages are English, German, Spanish, French, Hebrew and Arabic.
After selecting your preferred display language in the drop down, click the
apply
button at the end of general section to apply the language change.
e-mail
In this field you can enter your personal or company e-mail.
password and re-enter password
These two fields are used to change the current password. In order to change your password, you must enter the same new password in both password and re-enter password fields before clicking on the
apply
button at the end of general section.
The new password must contain at least one number, one uppercase letter and not less than 8 characters.
NFC
In this field you can enter an NFC tag id. This allows you to log in to ginstr apps by scanning this NFC tag on Android devices with built-in NFC technology.
first name and last name
In these fields you can modify first and last name which were entered on account creation.
mobile number
In this field you can enter your personal or company mobile number.
company (optional)
In this field you can enter the name of your company.
disable chat support
This checkbox disables support chat so that the chat window will no longer be displayed in either SSO or ginstr web.
delete all data of all tables in this account older than (days)
In this field you can define how long the data in all tables of all applications enabled for your account will be kept.
Default value is 0 which means that data will be kept in tables forever.
Value must be positive number up to a maximum of 999 days.
After entering the desired value, click the
apply
button at the end of general section to apply the change.
maximum number of rows that can be displayed in each table
Here you can define how many rows can be displayed in each ginstr web table before "filter by record creation date" appears in table. Once the defined number of records is reached in a table, the records in the table will be grouped based on record creation date. This number of records is defined on browser and server level.

hide/show content

hide/show content section

This section consists of a list of application tables with option to change permissions on each table and section where user can assign or unassign records that exist in table.

The hide/show content section consists of the following items:

list of ginstr applications
Here you will be shown a list of names of all ginstr applications which are enabled for your account.
list of tables of selected ginstr application
When you click on one or more application name in "list of ginstr applications", then all tables of the selected application(s) are displayed in "list of tables of selected ginstr application". For each table you can set the following permissions : create, read, update and delete (CRUD permissions). Here you have option to either enable or disable each permission for certain table by clicking each permission link. You can also select a table and then click on the "activate all" link above the list of tables to activate all permissions on the selected table.
If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web
list of records in selected table
When user select some table in "list of tables of selected ginstr application" part then "list of records in selected table" part appears with option to assign/unassign existing records in table.
When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on
apply
button above the ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web .
interface for defining how much days to keep records in tables on application and table level
Above "list of tables of selected ginstr application" part and "list of records in selected table" part there are fields where user can define how long data in all app tables or in single app table will be kept.
This feature exists on 3 levels
  1. all applications level (which exist in general section and is described there)
  2. single application level - this field exist above "list of tables of selected ginstr application" part and when some number of days is defined there data in all tables of that app will be kept for that number of days and after that deleted
  3. single table level - this field exist above "list of records in selected table" part and when some number of days is defined there data in that particular table will be kept for that number of days and after that deleted.
General rule: If define amount of days on level 1 then same amount of days will be applied on levels 2 and 3 for all apps. If define amount of days for some app on level 2 then same amount of days will be applied on level 3 for all tables of that app and for all other apps (and those apps tables) will be still applied amount of days defined on level 1. If define amount of days for some table on level 3 then this amount will be applied for that table only and all other tables of that application will have amount of days defined on level 2 of that application .

subaccounts

subaccounts section

In this section a main account user can create subaccounts. Amount of subaccounts which can be created by the main user is defined based on ginstr subscription. Main account is also called company account which means that, for example if a company has 10 workers which will be using application they will need to create 10 subaccounts on their main (company) account for each worker that needs to log in to application. The main account is used as an administrator for subaccounts created by that main account and can choose which applications subaccount can use and which permission the subaccount will have for each tables. The main account user can also delete subaccount created by that main account user.

The subaccounts section consists of the following items:

  • interface to add new subaccount and list of existing subaccount
  • list of applications enabled for selected subaccount
  • list of tables for selected applications
  • list of records in selected table


interface to add new subaccount and list of existing subaccount
When user click on "add subaccount" button on top of this section then interface will open where used can enter required data to create new subaccount.
  • In 'e-mail' field user should define e-mail which will be used as username of new subaccount.
  • In 'password' field user should define password which will be used by new subaccount for logging in. Under this field there is a checkbox labelled "show password" which, when checked will display the password in plain text.
  • In 'NFC' field user can define the NFC tag id which can be used by that new subaccount to log in to ginstr launcher and ginstr apps.
  • In 'role' drop down user can select some of roles which can be created by user and will be described in next section.
  • In 'applications' drop down user can select which applications will be enabled for subaccount
  • In 'access status' drop down user can select between active and suspended status. User can create unlimited number of subaccounts with suspended status but only that much subaccounts with active status as have allowed by ginstr subscription. Only active subaccounts will be possible to use ginstr web and ginstr apps.
  • In 'idle timeout (hh:mm)' field user can define amount of time after which if inactive subaccount will be logged out. Value should be set in range 00:20-24:00
  • Thecreating subaccounts allowed checkbox, if checked, allows subaccount to create its own subaccounts (This option is not yet supported)
  • 'user can use ginstr apps' and 'user can use ginstr backend' checkboxes allow the main account to define whether or not each subaccount will be able to use ginstr web and/or ginstr apps.
Once all data is filled and the
add
button is clicked, the newly created subaccount appears in this section.
In the list of existing subaccounts main user have option in the list to click on show settings link which opens interface to edit existing subaccount or can click on trash can icon which will delete existing subaccount
list of applications enabled for selected subaccount
This section displays the names of all ginstr applications which are enabled for that subaccount
list of tables for selected applications
This part is as described in hide/show content section.
When user click on some application name in "list of ginstr applications" part then all tables of selected application are displayed in "list of tables of selected ginstr application". For each table there are four permissions displayed: create, read, update and delete (CRUD permissions). Here user have option that by clicking on link with name of some permission either enable or disable that permission for certain table. Also user have option to select table and then click on "activate all" link above the list of tables and activate all permissions on selected tables.
If create permission is enabled on table this means that user will be able to create new records in that table. If read permission is enabled on table this means that user will be able to see that table in ginstr web. If update permission is enabled on table this means that user will be able to modify existing records in table. If delete permission is enabled on table his means that user will be able to delete records from that table in ginstr web
Main difference is that in hide/show content section tables are created with enabled permissions and in subaccount section tables are created without permissions so that main user can define permissions on tables for subaccount.
Both main account and subaccount are using same tables of applications so there are no two set of tables but only different permissions on same tables.
list of records in selected table
This part is same as described in hide/show content section.
When user select some table in "list of tables of selected ginstr application" part then "list of records in selected table" part appears with option to assign/unassign existing records in table.
When records are added to table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user click on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user click on
apply
button, the ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web.
Since same tables are used for both main account and subaccount records created by main account and all existing subaccounts of that main account will be displayed in this section but it can be defined per each subaccount here which records will be displayed in table for that particular subaccount

roles

roles section

In this section you can define different roles that can be assigned for that main user's subaccounts. Roles are templates of permissions and records assignments for apps and if role is assigned to some subaccount then tables permissions and records assignments defined in that role for certain app will be applied on that subaccount for that app if that app is enabled for that subaccount in subaccounts section. Once role is created it can be assigned to each subaccount (new or existing) in interface for adding/editing subaccounts. When in subaccount section in from some subaccount select role in roles drop down and save changes after that when click on that subaccount applications assigned to that subaccount will not appear on right side in "list of applications enabled for selected subaccount" part. This means that permissions and records assignments defined by role are now applied on that subaccount.

The roles section consists of the following items:

interface to add new role and list of existing roles
When you click on the 'add role' button, the interface for adding a new role opens with 'enter role name' and 'enter description' fields. Once you fill these fields and click on the
add
button, the new role is created and displayed in the list of existing roles.
Existing role has an option to 'show settings' which, when clicked enables you to edit the name and description of a role,a 'delete' button, which when clicked enables you to delete existing row and there are names displayed and total number of subaccounts assigned to that role.
list of applications enabled for main account
When you click on existing role then on right side appears list of all applications enabled for main account
list of tables for selected applications
When user click on some of applications from the list of applications enabled for main account part then in the list of tables for selected applications appear all tables of that selected app. Tables are displayed without enabled permissions so that user can define permissions.
For each table there are displayed following permissions : create, read, update and delete (CRUD permissions). By clicking on the link with name of some permission, you can either enable or disable that permission for certain table.
There is also the option to select a table and then click on 'activate all' link above the the list of tables and activate all permissions on selected tables.
If create permission is enabled on a table, this means that user will be able to create new records in that table.
If read permission is enabled on a table, this means that user will be able to see that table in ginstr web.
If update permission is enabled on a table, this means that user will be able to modify existing records in table.
If delete permission is enabled on a table, this means that user will be able to delete records from that table in ginstr web.
Permissions defined here will be applied on subaccount if that role is assigned to subaccount and it will override permissions defined directly on subaccount in subaccounts section
list of records in selected table
When records are added to a table they are assigned by default and they are listed in form of record id's in ASSIGNED list. If user clicks on some id in ASSIGNED list then that id moves to NOT ASSIGNED list on left side. When user clicks on the
apply
button above the ASSIGNED list then changes will be saved and record which is moved to NOT ASSIGNED list will not be displayed in table in ginstr web.
Assignments of records defined here will be applied on subaccount if that role is assigned to subaccount and it will override assignments of records defined directly on subaccount in subaccounts section