Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Div


Div
stylefloat:right;padding-right:20px;margin-top:-10px;width:33%;

Click the image to view a larger version.


Div
stylewidth:64%;

ShareVision is an web application built for Social Support agencies to collate, track and report data on their activities and enterprise. ShareVision is built on the Microsoft SharePoint platform with ShareVision proprietary features, pages and enhancements. Users can access the agency ShareVision site through a browser and internet connection with login credentials.

The agency ShareVision Site Administrator can configure security via user permissions that allow staff users to access specific pieces of information, add new records, edit existing records or delete records. Data can be queried on screen and exported. Complex, frequently required queries can be custom developed into reports.

The basic elements of a ShareVision site are;

  • The Structure of your Site
    • Web Site
      • Lists (Tables) within your site
        • Records (items) within the each list
    • Front-End' pages (for users to access forms)
      • Pages: these display the records /items to users in different ways.
      • Filter Pages: in essence these pages query a list (or lists) with criteria to then display the results of that query. The most common filter pages are those built with the Filter Page Wizard; these pages use the context of where the link/button is to base the query on. That is, if the link/button is on the QuickStart of an Individual, then the system can be configured to filter only items for that Individual. The page itself is dependent on whether an Individual(s) and/or Programs or Residence columns are present
      • Custom Filter Pages: these pages can be developed by ShareVision through consultation with you about the requirements. An example is 'byUser' (a page that filters to records of a list of the logged in user).
  • The Data Elements of your SIte
    • Individuals
    • Programs and Residences (the location(s) or service(s) your organization provides)
    • User Accounts (accounts of people who login to access/add data to your site)

The focus of data collection is anchored mainly at two points; the Supported Individual  and the location, or Program or Residencethe support is offered. Electronic forms (items) collect data on either the Individual, Program or Residence or both. These forms are collected in tables (lists) for all Individuals and all Programs and Residences and are displayed in filter pages so that a user can view, add and edit forms filtered for a specific Individual or Location (Program or Residence).

ShareVision conveniently collects all these Filter Pages within Individual and Program or Residence 'portals' where all forms and documents say, for a specific Individual, can be accessed, new items added and existing ones edited. These 'portals' stat points are the Individual Details Page, Program Details Page and Residence Details Page. Each of these filter pages displays relevant data from multiple lists for that specific Individual, Program or Residence.


...

Security permissions can be configured and are recommended where staff users will only view and access the Programs or Residences where the work. Granting these permissions will display the Program or Residence name(s) on the 'My Programs/Residences' page for the correct users to click through to the location Program Details page or Residence Details page.

See: Security Manager: Programs and Residences (Programs and Residences section)

...

When Individuals have been created within ShareVision either before  the Individual Wizard Permissions list has been configured or ShareVision has bulk imported the Individuals' data to create them, then you will need to manually configure permissions using the Security Manager: Supported Individuals Profiles tool.

See: Security Manager: Programs and Residences


Note

While the above describes the most basic setup, there may be other requirements that your organization has for when the site goes live for staff to use. These requirements may include and be extra to below;

  • The import of any historical data needed for planned reporting.
  • Any Profiles and Contact Details of people that interact with your organization that are not Individuals or Staff.
  • Any custom workflows that do not fit the 'one-form-at-a-time' model of ShareVision.
  • Any custom reporting outputs needed at 'Go-Live' date (e.g. a provincial reportable Incident form).
  • Any custom development changes to the basic template site that are not Site Administrator configurable.

In these requirements and others, your assigned Product Expert will guide you in this implementation project.

...


How do I create a form for staff to complete?


Div


Div
stylefloat:right;padding-right:20px;margin-top:-10px;width:33%;

Click the image to view a larger version.


Div
stylewidth:64%;

A form collects data to be stored in a list. Generally, before creating a new form, you will create a new list, then create columns to place in the form for your staff to enter data. The form is presented to staff users by a Filter Page, which you will need to configure in the Filter Page Wizard. If you do not have the Filter Page Wizard Add-On installed you can consult with your Product Expert about it.

In ShareVision a form is called a Content Type.

In ShareVision you can create multiple Content Types (forms) that share columns, collecting data for the one list. Each form can contain shared columns and columns unique to a content type. With multiple content types on a list, a Filter page can be configured for each content type using the Filter Page Wizard. Each filter page will filter the list to display for staff only the records (items) for an Individual, Program or Residence and a 'new form' link to create items.

ShareVision also provides the ability to use and create Site Content Types. These are essentially template content types that you can add to a list.

See: How to Create a New Form for Users

See: Form Extension Add-on

See: Form Header Add-on

See: Form Help Content Add-on


^ Top ^


...

The purpose of archiving is to keep Lists that grow rapidly to a manageable size, reducing the page load times without permanently deleting historical data. Archival records cannot be used in reports or any other areas of your ShareVision site. Archives should also not be used as a backup of your data, but rather as a repository for old records.

Archiving Add-On

The Archiving Add-On aids the archiving process in your ShareVision site providing a simple tool that allows you to choose the list and the date period of data to capture, while giving the option to delete archived data from the list at the end of the process. The Archive tool will then replicate the list by creating a new list called “Archived- *List name*” in the Archived lists section of your ShareVision All Site Content page.

...

See: Document File Management and Uploading

Top ^

STAFF ACCESS and OTHER USER ACCESS 

Jira Legacy
serverJIRA (sharevision.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId3fb75880-5785-3f69-afca-952a52a99b81
keyKB-17
Wahl

How do I give a new staff member access to ShareVision?

...


...


How do I give a new staff member access to ShareVision?

Granting someone access to your ShareVision site is the basis of the security of the personal data stored on the site, and requires planning and understanding of the security model. There are several tools to assist with this to help make the management of site security more straight forward. All access is granted through the application of site permissions. To fully understand ShareVision security it is important to understand Site Permissions and how they are applied.

There are several steps involved which work in concert to provide access to a ShareVision site:

...

.

Understanding Permissions
Permissions are the rules that get applied to other security devices (groups and/or user accounts) applied by site administrators which allow certain access and/or actions to be performed by users (e.g., Read - can only read items they have access to, No Delete - can add/edit items with no ability to delete, Contribute - can add/edit/delete, etc.). ShareVision comes with a standard set of permissions that have generally proved to be flexible enough for most client applications. They can be further customized or new permissions can be created.

See: Site Permissions
See: Inherited Permissions
See: Editing Permissions


There are four steps to grant a staff member access to a ShareVision site:

  • Creating User Login Accounts;
  • Creating Security Groups;
  • Assigning permissions to Security Groups;
  • Adding User Accounts to Security Groups.


Creating a new User Login Account
Each person who needs access to your site should be given their own, unique account for logging on to the site. The account includes User Information which includes;

...

See: Create a new user from the Site Actions menu

See: Create a new user from the Contact Manager

...

Assigning permissions to Security Groups.
Depending on the intended purpose of the group, permissions may be granted to specific lists, or individual items within a list. In some instances a group will have certain permissions granted across the bulk of items on the site but, in order to restrict access to certain information, some groups are used to allow selective access to smaller sub-sets of information (e.g., to the data for a single, supported individual, program or residence) that has been isolated from the rest of the site by breaking security inheritance and applying unique permissions.

There are also tools to help manage this process which tools that provide more options for applying intricate permissions in bulk operations. Security Manager: Programs and Residences; Security Manager: Supported Individuals Profiles; Intake New Clients Wizard.

See: [ Security ManagersManager: Programs /Residences, and, Supported Individuals | https://sharevision.atlassian.net/wiki/display/SHARESUP/Security+Manager]
See: [Intake New Clients Wizard | https://sharevision.atlassian.net/wiki/display/SHARESUP/Intake+New+Clients+Wizard]and Residences

See: Security Manager: Supported Individual Profiles

See: Intake New Clients Wizard


Adding User Accounts to Groups.
It is possible to add users directly to a group by editing the group (;

Site Actions > Site Settings > People and Groups > if necessary, click on Groups link [top of navigation links] > select a group to add a user to > New [on toolbar]).

Groups are used to provide permitted access to various elements on the ShareVision site. This provides an easier method of granting access for users to select parts of the site than creating unique permissions for each and every user added to the site. For example a group can be created for, and granted permission to, a specific program and all Individuals participating in that program. staff who should have access to that program and the

Individuals attending that program have their user account added to the group and automatically will have permission to everything that the group has access to. If a staff takes on responsibilities for another program their account can simply be added to the group for that additional program (and removed from the current program group, if that access is no longer required).

See: [Managing Group membership by User | https://sharevision.atlassian.net/wiki/pages/viewpage.action?pageId=14581849] View & Edit Groups By User 


Top ^

SECURITY: LEVELS and PERMISSIONS to access specific information. 

Jira Legacy
serverJIRA (sharevision.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId3fb75880-5785-3f69-afca-952a52a99b81
keyKB-5
Wahl

How do I restrict users access to specific Supported Individuals they support?

Top ^

...


...


How do I restrict users access to specific Supported Individuals they support?

There are two groups of settings you can use to restrict the access of staff users to specific Individuals; security permissions and the My Individuals QuickStart icon settings.

Security Permissions

Access (and visibility) to Individual by a Staff User is configured by changing the permissions on the Profiles list item for the Individual. This change is made by breaking the inheritance of permissions the Profile item has with the Profile list permissions. Single user accounts can be given access while security groups of user accounts can also be given permission to access specific Individuals. Permissions to Individuals can be effected three ways;


Individual Wizard Permissions

This is a list used by the Intake New Clients Wizard feature that applies pre-defined permissions to new Individuals being added to the system and a residence or program, or, when an existing Individual within the system is added to a new program or residence. This list needs to be defined for permissions to take effect.


Security Manager: Supported Individual Profiles.

A tool for Site Administrators to bulk manage permissions on multiple Individuals' Profiles list items.

See: Security Manager: Supported Individual Profiles


Profiles list item manual permissions configuration.

While it is recommended to use the above methods of effecting permissions changes, there may be occasions where the Site Administrator has a need to go to the Profiles list, find an Individual's Profile item and make permissions changes.

Navigate to Site Actions > View All Site Content > (lists) Profiles > (item of Individual) View > Manage Permissions

'My Individuals' QuickStart Icon

It is strongly recommended to configure permissions as described above. An extra step can be taken to ensure Staff Users can only view and access Individuals via the locations these Individuals participate with your agency. That is, the Staff User would have to click on a Program or Residence to then see the list of Individuals' names within that location. From there they can click an Individual's name to view their Individual Details page.

This is achieved by hiding the 'My Individuals' QuickStart Icon and therefore no link to the Individuals list page.

See: Quickstart Menu, Navigation Bars & Icons v.3.5 & 3.7#QuickStartMenuIcons-Manage


Top ^

...


How do I restrict users access to specific Program(s) and/or Residence(s) the work at?

To restrict staff user access to specific Programs and Residences the Programs and Residences list item(s) permissions need to be configured (edited). There are two ways that this can be done;


Security Manager: Programs and Residences.

A tool for Site Administrators to bulk manage permissions on multiple program or residence Program and Residences list items.

See: Security Manager: Programs and Residences


While it is recommended you use the above method to make any changes to permissions, you can effect the same changes by navigating directly to the Profiles list and changing permissions on each item separately.

Programs and Residence list item manual permissions configuration.

While it is recommended to use the above methods of effecting permissions changes, there may be occasions where the Site Administrator has a need to go to the Profiles list, find an Individual's Profile item and make permissions changes.

Navigate to Site Actions > View All Site Content > (lists) Programs and Residences > (item of Program or Residence) View > Manage Permission


Note

See: How to Set Up Security for a New Program or Residence


Top ^


...

I can't configure the system to suit our process. Can we customize ShareVision for our unique needs?


Note

If you are a ShareVisionEssentials customer, customization of your site is limited to altering the five (5) included reports. Please contact our Support Team through the Support Portal with as much description as possible and a Product Expert will contact you to discuss this further.

...