SharePoint Column/View Permission provides further protection on list columns and views than the SharePoint permission system does. Using it, you can safeguard the confidential column contents from access and edition by unauthorized users.

With SharePoint Column View Permission 3.0, we've added over 8 features — taking this best tool to a whole new level

Set Default View For Users

Column/View Permission 3.0 now supports to set default view for the selected users. Once configured, user will visit the specified default view on login.

Column/View Permission API

Column/View Permission 3.0 publishes an Application Programming Interface (API) to be compatible with other applications, and is now compatible with SharePointBoost Batch Check Inversion 2.0.

Add Extral Protection against Access from Web Services

Column View Permission can now work properly in the applications which use object model or web services of version 3.0 or above.

1. Column Permission Feature Introduction
• 1.1 Column Permission
• 1.2 Permission Settings
• 1.3 Advanced Settings
• 1.4 Import or Export
• 1.5 Add Column Permission Part
• 1.5.1 Permission Settings Name
• 1.5.2 Include/Exclude People
• 1.5.3 Conditions
• 1.5.4 Form Permission Settings
2. Column Permission Example
3. Hide columns in Alert Me email
4. View Permission Feature Introduction
• 4.1 View Permission
• 4.2 Default View Permission Level
• 4.3 View Permission Redirect Page
• 4.4 Import or Export
• 4.5 Add View Permission part
• 4.5.1Permission Settings Name
• 4.5.2 Include/Exclude People
• 4.5.3 View Permission Settings
• 4.5.4 Default View
5. View Permission Example
6. Column/View Permission API
7. Control Column/View Permission of Web Service

Please note that Permission Workflow has to be activated before it can be used. For further reference, please see our Product Installation Guide.

Please note: Column/View Permission settings will not take effect for site collection administrators, System Account and for users granted Full Control by the permission policy in Central Administration.

Further information is also available in our FAQ.

1. Column Permission Feature Introduction

1.1 Column Permission

This function lets the administrator globally enable or disable the Column Permission settings configured with Column Permission in this list.

1.2 Permission Settings

The Permissions Settings section gives the administrator an overview over all Column Permission settings already set up. Each settings part can be deleted, enabled or disabled. The status field displays whether a settings part is enabled or disabled. To edit a Column Permission settings part click the name of the settings part,this will open the settings page for the Column Permission settings part.

To add Column Permission settings, click.

1.3 Advanced Settings

The Advanced Settings section gives the administrator option to decide if the read-only columns can be edited on the object-model level, or by applications which use object-model.

To prevent editing read-only columns on object-model level, select "No" option; otherwise, select "Yes" option.

1.4 Import or Export

Import/Export permission part function is based on XML files.

To import settings click the Import button. In the popup window, administrator can either paste the XML file contents into the designated area, or browse for a file and upload it. To confirm the XML file importation click the OK button. To abort importing the specified permission settings, click the Cancel button.

To export permission settings click the Export button. A popup window will open and display the XML file contents in the Edit area. The administrator can then save the settings to any location and thus make it reusable in other lists.

1.5 Add Column Permission Part

1.5.1 Permission Settings Name

Name each Column Permission settings part. The settings part will be displayed with its name in the Permission Settings table in the main settings page for Column Permission.

1.5.2 Include/Exclude People

The User/Group selection process is divided intwo parts: Include People and Exclude People.

The Include People section lets the administrator decide if he wants to include all users, or if he wants to select a small group of users based on criteria that he specifies.

The Exclude People section helps the administrator to decide which users are excluded from the permission settings.

Both Include People and Exclude People sections contain the same components.

Column View Permission allows selecting all users or selecting specified users by filtering them as follows:

• Including anonymous users
• Input of user or group names
• Selecting user/group columns, as well as relative lookup fields in this list
• Looking up users from other lists and filter them based on conditions

a) Anonymous Users

This allows administrator to include anonymous users in the permission settings.

b) Input of user and group names

Column View Permission allows entering multiple users or groups; administrator can look up names or check the names entered into the box.

c) Selecting user/group columns, as well as relative lookup fields in this list

This function is provided to assign permission to Person or Group columns which present users or groups.

Checking checkboxes next to the Person or Group columns will result in selecting the users which are contained within the selected column. This selection will filter the values in the column specified with the logged in user. The permissions are only set for items associated with the currently logged in user, but will not affect any other item.

The administrator can also select Person or Group columns from related list if the checkbox next to "Also display User Group columns in other lists related to Lookup columns in this list"is checked. This means that all user/group columns in the list that is looked up from will be available for selection.

d) Looking up users from other lists and filter them using conditions

The process to select users from another list includes 3 steps:

• Specify the list to look up from. To do so, the administrator has to firstly select the site on which the list is located. Note that only sites in the same site collection are available.
• Specify the User/Group columns that will be used to specify the users. These are to be selected through checkboxes, similar to the User/Group column selection in the original list. The difference is that all the users are pulled from the column regardless of the user who has logged in. Thus the settings will be the same for all items. Also, related columns are not available to select in these settings.
• A final step is the ability to filter a selection of users using conditions.

1.5.3 Conditions

Two conditions types are provided in settings page, Basic and Advanced.

The Basic conditionshelp administrator to easily configure conditions.

The Advanced conditions provide more operators and functions to implement elaborate conditions beyond basic conditions.

1.5.4 Form Permission Settings

Column View Permission allows the administrator to specify what columns are accessible in what way for each form. Administrator can set columns hidden or read-only in New Item Form, Edit Item Form and View Item Form.

Column Permission and View Permission are working closely together. This means that columns hidden from certain users will have to be removed from a view if these users should be able to access this view. If a view contains these columns it will not be accessible by users.

2. Column Permission Example

Here is a list that keeps confidential HR information.

The screenshot above illustrates this issue; here some information is included that normal employees should not be able to view or change.

To change this behavior, navigate to the Column Permission Settings. To do so, enter the List Settings page.

Note: To configure the Column View Permission, you should be the member of site or site collection owner, or have Full Control permission on the list.

Here is a list that keeps confidential HR information.

Firstly specify the name of the permission part; here it is called "Administration".

Here, all SharePoint users except HR department should be limited to view or edit the columns so, in the Include People section, the radio button is to be set to "Select All Users".

To exclude account, tick "Exclude People" checkbox.

Here we exclude employees in the HR department. To do so, select

Then select HR Info list from HR site.

After that, a column has to be selected from which the users or groups are pulled from. The "Account Name" column contains all the users in the company; therefore this information has to be filtered. For filtering this information, Column Permission provides condition settings. The condition in this case is:

This condition specifies that only users working in the HR department will be selected.

To complete the settings you have to specify what permissions the users should have for which form.

Here we set columns hidden or read-only for each item form.

After all settings have been made, confirm by clicking OK. Please note that you also have to click OK in the Column Permission main settings page to confirm any changes made.

Log in as a user who is not working in the HR department. The New Item Form now does not display any column to edit, it is completely empty.

In the Edit Item Form, only the columns set as read-only are displayed, all others are not shown anymore. The columns displayed cannot be edited at all.

Columns which are set as hidden in View Item Form cannot be viewed.

As Column Permission is linked with SharePointBoost's View Permission, views containing columns that are hidden from users will be not accessible.

3. Hide columns in Alert Me email

Column/View Permission version 3.0 and above now support hiding columns in Alert Me emails.

To use this feature, in central administration, activate the "Column Permission for Alert Me" feature for web applications.

Once the feature is activated, columns will be automatically hidden in emails based on the Column Permission configuration.

Note: after installation or upgrade of Column/View Permission version 3.0 or above, Timer job service should be restarted on each server of farm.

4. View Permission Feature Introduction

4.1 View Permission

This function lets the administrator to globally enable or disable View Permission settings configured in this list.

4.2 Default View Permission Level

This function defines the default behavior for View Permissions. If the default level is set as "Hidden" then existing and new views will be hidden by View Permission settings unless the administrator specifically set these views full access or read-only. Setting the default to be "Visible" will thus allow all new and existing views to be accessible by default. Also, administrator can set permissions for each view in the Permission part.

4.3 View Permission Redirect Page

These settings give the administrator the option to configure notifications if views are unavailable to users. Check the "Use redirect page" to use this feature. If activated, any users without sufficient permissions will be directed to a page presenting him with the following options.

There are four messages that can be configured. However, for each message a default message is preset.

• The "View unavailable message": This message will be displayed if the user does not have sufficient permissions to access the view selected.
• The "All views unavailable message": This message will be displayed if the user does not have sufficient permissions to access any view for this list.
• The "'Go to view' button text": This message will be displayed on the 'Go to view' button, to direct the user to the next available view.
• The "'Return to homepage' button text": This message will be displayed on the 'Return to homepage' button to direct the user from this list.

4.4 Import or Export

Importing and exporting permission parts for View Permission works in the same way as for Column Permission (see above).

4.5 Add View Permission part

To add view permission settings, click in view permission main page.

4.5.1Permission Settings Name

Specify a name for the view permission settings part.

4.5.2 Include/Exclude People

The User/Group selection allows administrators to specify which users to include or exclude from the selection process. In "Include People" section, administrators have the option to:

• Include/exclude anonymous users
• Enter user or group names
• Look up users from other lists and filter them using conditions

Selection parts for View Permission functions in the same way as Column Permission (see above).

4.5.3 View Permission Settings

In the View Permission Settings, administrator can specify the permission level that users will have for each of the views in a list.

The Access Type defines whether the view should be fully accessible, read-only (Disable Edit View), or hidden for the selected users. (Please note that setting a view as read-only will mean that no items in the list can be edited or deleted unless the user has the appropriate permissions. Also, the "modify this view" option in the Views dropdown menu will not be available for thisview).

Administrator can check "Disable create view" option to prevent users from creating views in the list, including public view and personal view.

Administrator can also decide which ribbon buttons are not available for users by setting the iconsto "disabled" status.

4.5.4 Default View

In the Default View settings, the administrator can specify the default view for selected users in "Include People" section.

After configuration, the logged on users will visit the specified default view when they try to access the list.

5. View Permission Example

In companies there is information that should only be accessible to certain people. So only staff in the HR department has to be able to read and modify private information of employees. Other employees should not be able to access this kind of information.

The views containing private information should be hidden for all users except HR department.

A way to achieve this goal is to define views that include the necessary information for its target audience, and then restrict the access level with SharePointBoost View Permission.

First, create a view that will be accessible for all employees. This view is called "General Info".

Then, create another view for HR staff only; this one is the "Detail Info".

The "General Info" view includes no sensitive information, while the "Detail Info" view displays all columns for the HR Department. To set permissions for these views, navigate to the "View Permission" settings page.

Note: To configure the Column View Permission, you should be the member of site or site collection owner, or have Full Control permission on the list.

Note:

In the List Settings page click on the "View Permission" link to be directed to the "View Permission" general settings page.

The administrator has activated the Redirect Page, so that users are informed of their choices when they navigate to a view for which they do not have permission.

Then navigate back to the View Permission main settings page, and click "Add View Permission Settings". The administrator creates a settings part that allows users access the "General Info" view, while denying access to other views that contain confidential information. This settings part is called "General View".

Then administrator has to specify which users will be affected by these view permission settings. As all employees should be able to access this view the administrator just selects the "Select all users" radio button.

For "Exclude People" section, employees working in the HR department should not be affected; they are excluded using the following condition:

Now the administrator has to select which views are available to the employees, and which permissions they have for these views.

Also, administrator limitsemployees to create views both public and personal by checking "Disable create view" option.

In this view permission part, administrator wants employees to visit "General Info" view by default.

Then, the administrator still has to set up the view permissions for the HR department. Firstly, again, create a new View Permissions settings part. Name it "Detail view".

Then, select which users to include. Here the view permission is only for HR department, so, select "Select Only the Following Users" option.

And then, select the employees working in the "HR" department using the following condition:

Now, the administrator has to specify what access type the HR employees should have for each view.

Because the administrator wants the HR employees to visit a different view by default, select here"Detail Info" view in "Default View section".

Logging in as Mike from the Development department, only the "General Info" view is available. Also, the actions in ribbon are disabled.

On the other hand, if Laura from HR department logs in, she visits "Detail View" by default. She can access all views and has permissions to click ribbon buttons.

6. Column/View Permission API

Column/View Permission 3.0 publishes an Application Programming Interface (API) to be compatible with other applications.

For more details, please refer to Column/View Permission 3.0 API Documentation.

7. Control Column/View Permission of Web Service

For 3.0 version, Column/View Permission will limit permissions of web service methods base on the Column/View Permission settings in the list.

Service	Methods	Description
Lists (Lists.asmx)	AddAttachment DeleteAttachment GetListAndView GetListItems UpdateListItems GetListItemChanges GetAttachments	Methods for working with Lists and List Data
Site Data (SiteData.asmx)	data from sites or lists GetAttachments GetListItems	Methods that return metadata or list
Views(Views.asmx)	AddView DeleteView GetViewCollection GetViewHtml UpdateView UpdateViewHtml UpdateViewHtml2	Methods for working with list views

To enable Column/View Permission on web services, you need to install Column/View Permission for Web Service on each web front end of farm.

How to install Column/View Permission for Web Service,please refer to Column View Permission for Web Service Installation Guide..

Top

Languages Supported: English, Japanese, German, Simplified Chinese

System Requirements

For SharePoint 2010:

Operating System:	Microsoft Windows Server 2008 x64 Microsoft Windows Server 2008 R2
Server:	SharePoint Release: - Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010 - Microsoft SharePoint Foundation 2010 SP1 or Microsoft SharePoint Server 2010 SP1 - Microsoft .NET Framework 3.5
Browser:	Microsoft Internet Explorer 7 or greater is recommended for Advanced admin features Mozilla Firefox supported Google Chrome Supported

For SharePoint 2007:

Operating System:	Microsoft Windows Server 2003 x86/x64 Microsoft Windows Server 2008 x86/x64 Microsoft Windows Server 2008 R2
Server:	SharePoint Release: - Microsoft Windows SharePoint Services v3 (WSS3.0) SP2 or Microsoft Office SharePoint Server 2007 SP2 - Microsoft .NET Framework 2.0 or greater Note: This product is not compatible with SPS 2003 and WSS v2
Browser:	Microsoft Internet Explorer 6 or greater is recommended for Advanced Administration features

Technical Notes:

• Column/View Permission does not protect metadata in documents opened with external applications (Microsoft Office Word);
• No mobile support;
• Column/View Permission does not work for search results;
• Column/View Permission does not support RSS feeds;
• Cannot hide columns in Alert Me email for deleted items;
• Column with comma cannot be support by IndexOf() function.

Release Notes

3.3.427.0 Apr 27th, 2012	New Feature: - Support [Me] field in condition for Column/View Permission. Bug Fixed: - Contents in Multiple line of text column with "Append Changes to Existing Text" enabled cannot be saved in some situations. - JavaScript error occurs in New/Edit Item Form when hidden/read-only multiple line of text column with "Enhanced rich text" enabled. - JavaScript error occurs in New/Edit Item Form when hidden/read-only first column.
3.2.327.0 Mar 28th, 2012	Bug fixed: - Access denied occurs when user tries to enter the permission part which contains external list. - Conditions for external list part does not work.
3.1.1227.1 Dec 28th, 2011	New Features: - Support Japanese. - Support German.
3.0.1215.0 Dec 21st, 2011	New Features: - Support web services; - Publish Column View Permission API, and compatible with SharePointBoost products; - Read-only column on object model level; - Specify default view for every user; - Disable create or edit view; - Support Alert Me; - Read-only column content on datasheet view; - Seamlessly package list settings within site and list templates. Bugs fixed: - Column View Permission does not work on metadata columns; - Access Denied error occurs when user try to enter My Settings page after product feature is activated; - Merge Documents view cannot be hidden in Form library; - User with contribute permission cannot create personal views in the list.
2.3.1215 Dec 16th, 2010	New Feature: - Support German.
2.2.811.0 Aug 9th, 2010	New Feature: - Announced compatibility with SharePoint 2010.
2.1.715.0 Jul 15th, 2010	New Feature: - Server license added.
2.1.528.0 Jun 7th, 2010	Bugs fixed: - When editing a view, uses intended to "Group By" by using an invisible column, the view failed to be hidden; - Users could not get access to "People and Groups" even though having been assigned "Full Control" to the site and the site collection; - Given Column/View Permission had been activated, the workflow created by SharePoint Designer could not work properly.
2.0.401.2 Apr 2nd, 2010	New Features: - Allow for assigning form-level permissions; - Offer conditions to determine the users and user groups that will be assigned custom permission settings; - Import or export permission settings as an XML file.
1.17.1209.0 Dec 15th, 2009	Bug Fixed: - An error happened when users intended to enter into a list with previous column/view permission configuration after the site collection that the list belonging to being exported and then imported.
1.16.916.0 Sep 16th, 2009	Bug Fixed: - A column might be invisible to all the users though it was supposed to be invisible only to certain person.
1.16.820.0 Aug 21st, 2009	Licensing module upgraded.
1.15.428.2 Apr 28th, 2009	New Feature: - Add items’ URLs to certain fields. Bug Fixed: - Removed groups from site user count.
1.14.113.1 Jan 13rd, 2009	Bug Fixed: - Web part connection failed in customized forms when applying column permission.
1.13.112.0 Jan, 12nd 2009	Bugs Fixed: - Folder parameter was lost when changing view when applying column permission; - Stopped supporting XLST form and XLST view, only support customized forms which are composited by Form Field or List Iterator).
1.12.1226.1 Dec 26th, 2008	New Features: - Fully support customized forms; - Allow users to set permissions on attachments.
1.11.1204.0 Dec 5th, 2008	New Feature: - Availability of farm license.
1.10.1125.0 Nov 25th, 2008	Bug Fixed: - User fields could not be assigned permission in some cases.
1.9.1121.5 Nov 21st, 2008	Bugs Fixed: - Some views were hidden though they should be visible in those cases; - Improve performance for batch permission settings.
1.8.1104.0 Nov 4th, 2008	Bug Fixed: - Resolved the error happened when a view had an empty title.
1.8.1031.1 Oct 31st, 2008	New Features: - Support column permission for anonymous; - Allow users to assign permissions to list views.
1.7.0.3787 Oct 15th, 2008	New Feature: - Support assigning column permissions to user/group columns in a list. Bugs Fixed: - Resolved the error happened when users logging in as anonymous; - User lists were too long and no new line when assigning permissions to many users.
1.6.0.3709 Oct 10th, 2008	New Features: - Allow AD groups who are not in SharePoint site to be assigned column permissions; - Allow assigning column permissions to all users except specified ones. Bug Fixed: - Fixed errors in page title and description.
1.5.3.0 Aug 18th, 2008	Bug Fixed: - Resolved the errors happened when inserting an image into a new item, but failing to save the new item.
1.5.0.0 Aug 18th, 2008	New Feature: - Enable all workflow association when activating workflow features.
1.4.1.0 Aug 11st, 2008	Bug Fixed: - Column permission could not work on Survey list.
1.4.0.0 Aug 7th, 2008	New Feature: - Split SharePoint Permissions Boost into three products (SharePoint features).
1.3.0.0 Jul 18th, 2008	New Feature: - Availability of a new product – SharePoint Item Permission Batch.
1.2.1.0 Jul 18th, 2008	Bug Fixed: - Increase the performance when users applying permission settings to lists which contained a great amount of items.
1.2.0.0 Jul 8th, 2008	New Feature: - Separate column permission settings from workflow settings, and add a link of column permission settings in list edit/setting page.
1.1.0.0 Jul 2nd, 2008	Initial Release

• Does column permission work even though I am using a customized edit form(By MS Designer)?
  • Yes, it supports customized edit forms.
  • When the columns in the customized form are represented as form field label, the column permission can work on this form, else if, the column permission does not work.
• Why do users have an "Access Denied" error when they try to connect to enter a view?
  • TIf all views of a list contain invisible columns, the list views will also be invisible to these users or groups. When he/she tries to enter this list he/she will receive an Access Denied error. Log in with site collection administrator and add/modify view to remove all invisible columns from it, then retry with the user account.
• Why can’t the list be edited in the datasheet after applying column permission settings?
  • If the list view contains selected read-only columns, the view cannot be edited in the datasheet or MS Access by these users or groups (menu items in Actions menu will be hidden).
• Does the SharePoint Column/View Permission work with document libraries in WSS 3.0?
  • Yes, SharePoint Column/View Permission can work with document library in WSS 3.0.
• If I want to limit a large number of users’ column permissions (except for a few ones), do I have to enter all the users’ names into the users/groups edit box?
  • No, you can enter the excepted users’ names into the users/groups edit box, and then select the "Users except above are limited to following columns" checkbox.
• If I have the "save versions" option enabled and I change something in an invisible column, can everyone see the changes through "versions"?
  • Yes, currently the "SharePoint Column Permission" cannot support hiding columns in the versions page. Alternatively, you should set the "View Version" permission to items by yourself.
• What does the "Created by"/"Modified by" option refer to?
  • "Created By" and "Modified By" are the inner user fields of an item (list). They represent users related to the item and can be assigned column permissions. You can add other user fields to the list so that you can assign column permissions to users who are represented by these user fields. All other products in the "SharePoint Permissions Boost" provide same functionality to make it more flexible.
• Is there a way to tell how many licenses are remaining when we start enabling the software and adding users on some sites?
  • Yes. There is a link at the bottom of the "Column permission setting" main page, click it you will be directed to license management page
• When I make the columns invisible for a specific group will they show up when the user creates a new item, or only in edit form?
  • The columns you set invisible to a user will not be show when the user creates or edits an item.
• Will Column Permission stop working if my license is expired?
  • Column Permission will not stop working when your license is expired. But if you need to modify the column permission settings, you will need to purchase a license.
• Can I use SharePoint Column Permission to set permissions in Word, Excel Access etc. desktop software?
  • SharePoint Column Permission cannot control the permissions in Word, Excel, Access etc. desktop software, because SharePoint does not provide an inner column permission mechanism.
• Does it work with webpart?
  • Yes, it works with web part.
• How does Column/View Permission work in datasheet view?
  • In version 2.0, when user tries to enter a datasheet view which contains read-only columns, Access Denied error will occur.
  • In version 3.0, user can enter datasheet view which contains read-only column, but the changes of content of read-only columns will not be saved.
• Why does Column/View Permission not work sometimes?
  • The issue may occur for the following reasons:
  • a. The solution is not deployed correctly, or the product feature is not activated.
  • b. The product does not take effect on the admin account or users in the Administrator Group.
  • c. Since Column/View Permissions can only specify permissions on UI level, it will not function on the forms created with SharePoint Designer or 3rd party products.
  • d. If the Site Action menu is customized by administrator, the Column Permission will possibly not work on the site.
• How can I prevent user to edit read-only columns with customized workflow?
  • Sometimes, the customized workflow modifies columns content on object-model level. If you do not want to edit content of read-only columns, select "No" option in Advanced Settings section in Column Permission Settings page.
  • 
• How does Column/View Permission work with web services?
  • In version 3.0, once Column/View Permission for Web Services is installed, the column and view permission will be controlled on web services.
  • This means user cannot view or modify hidden or read-only columns and views in conformity with the Column/View Permission configuration.
• How does condition setting work in Column/View Permission?
  • Column/View Permission determines if the columns content is read-only or hidden based on the condition.
  • If the condition is satisfied, the column will be set read-only or hidden in item form and list; otherwise, the columns will be visible or editable in item form and list.

Purchase FAQ

Questions about Licensing:

• What is the difference between a Server License and a Site Collection License/Farm License?
  • Currently, we can provide Server License, Site Collection License and Farm License:
  • Each WFE will require a Server License (For SharePoint 2007: all servers running the SP Web Application service will need to be licensed; for SharePoint 2010: all servers running the "Microsoft SharePoint Foundation Web Application" service will need to be licensed). SPB Server Licenses do NOT limit the number of end-users.
  • A Site Collection License (with end-user number limit) can be applied to one site collection only, you would need to make sure the number of end-users is within the end-user number limit provided by your license;
  • A Farm License can be used across all site collections within a SharePoint farm; however the maximum number of users within each site collection is limited by the end-user number limit provided by your license. For example, a 400-end user Farm License means that the number of users within a site collection should not exceed 400.
  • To find out the number of end-users you have in your site collection/farm, please check the license management page (this will appear after you install the trial version of our software on your SharePoint servers), or download and run the free End User Viewer Tool available here: http://www.sharepointboost.com/end-user-viewer-tool.html.
• Which type of license should I choose?
  • Server Licenses are better if you would like to use the product without site collection or end-user restrictions.
  • A Site Collection License/Farm License is better if you only want to use the product in one site collection/farm and the number of end-users is unlikely to grow rapidly or change frequently.
  • If you are still unsure as to which license type is best for you, please email sales@sharepointboost.com for assistance.
• What are "end-users" and how do they affect my Site Collection License/Farm License?
  • End-users do NOT affect Server Licenses. An end-user count is only needed for a Site Collection License or Farm License.
  • An end-user is defined as any user who has access to, or has accessed any site in your Site Collection/Farm at any point in time, either directly (e.g. signing in) or indirectly (e.g. assigning him a task). And the number of end-users in the site collection means the total number of users across all sites in the site collection.
  • Once a user has accessed a site in the site collection/farm, he is counted, regardless of whether or not this user is active on the site where the product is used. For example, while you may only have 50 users who would need to use the product on Site A in the site collection, there are 360 users accessing Site B (including the 50 accessing Site A), making a total of 360 users with access to the site collection. Since Site A and Site B are in the same site collection, you would need to purchase a license for at least 360 users. SPB licenses increase in increments of 100 users, so if there are 360 people who have access to the site collection, you will need to purchase a 400 end-user license.
• If the current end-user number exceeds the end-user number allowed by my Site Collection License/Farm License, what will happen?
  • Please note that end-users do NOT affect Server Licenses.
  • If the current end-user amount exceeds the amount of end-users allowed by your Site Collection License/Farm License, the original functions and settings of the software will NOT be influenced until you change them (e.g. additions, deletions, modifications, etc.)
  • You can either use our End User Viewer Tool to delete some inactive or disabled SharePoint users (http://www.sharepointboost.com/end-user-viewer-tool.html) or upgrade your license with more end-users.The cost of a license upgrade is equal to the price difference between the old and new licenses, plus a standard fee of 50 USD applied to all upgrates submitted. For example, if you had purchased a 200 end-user license for $500 and now you want to upgrade to a 300 end-user license (Price: $600), you only need to pay the difference (600-500=$100) plus the standard upgrade fee ($50), therefore in total $150. It also applied to Farm License.
• What will happen if I buy a new server or add another server? How will this affect my license?
  • Please note that adding an additional server/replacing an old server with a new one will NOT affect Site Collection Licenses/Farm Licenses. Please contact sales@sharepointboost.com for more information only if your Site Collection ID/Farm ID has changed.
  • However, if you are using Server Licenses for an SPB product and you subsequently add an additional WFE to your environment, you will need to purchase another Server License. Also, if you elect to replace an old server with a new server, and the Server Code subsequently changes, you will need to contact sales@sharepointboost.com for more information.
• What is Premium Annual Support? If I buy it, what do I get?
  • For detailed information regarding SharePointBoost's Premium Annual Support plan, please visit our support page.
  • Premium Annual Support must be renewed each year. Support fees are charged per license per year.
• How can I find my Server Code or Site Collection ID/Farm ID?
  • To find your Server Code or Site Collection ID/Farm ID, please check the license management page (this will appear after you install the trial version of our software on your SharePoint servers – for help finding this information, please email support@sharepointboost.com, or download and install the free License Management Center here: http://www.sharepointboost.com/licensecenter.html.
• What is the price for DEV/Test environment? Is there any discount?
  • SharePointBoost offers 50% discount off the list license price for DEV/TEST environment when customers purchase license for their production environment.
• Do I have to pay for updates as new versions of the product are released?
  • Do I have to pay for updates as new versions of the product are released?
  • A minor release contains bugs fixes and minor feature changes (e.g. 1.0 to 1.1). Major releases include significant feature additions and enhancements (e.g. 1.x to 2.0), and Major releases (usually with significant functionality added) require the payment of an upgrade fee. However, if you purchase our Premium Annual Support plan, then all major and minor releases are free for one year.
• Do I need to apply for a new license if the site collection ID/farm ID/server CODE has been changed?
  • Yes. Since the license is generated based on the specific site collection ID/farm ID/server CODE, which means, once the site collection ID/farm ID/server CODE is changed, the original license CODE would be invalid as well. You need to contact our sales team(sales@sharepointboost.com ) for further assistance.

Questions about Purchasing Process:

• Does SharePointBoost accept Purchase Orders?
  • Yes, we accept purchase orders from our customers, for more details on purchasing via PO, please contact sales@sharepointboost.com.
• Which payment methods does SharePointBoost allow?
  • PayPal:
  • The preferred method of payment is PayPal. You can either purchase SharePointBoost products via PayPal account or via credit card. If you would like to purchase a Site Collection License/Farm License where the total number of end-users is greater than 900, we will generate a PayPal purchase link and send it to you in an email (paying via purchase link does not require that you have a PayPal account).
  • Secure Purchase Link:
  • If purchasing our products through PayPal is not possible for you, then you may contact sales@sharepointboost.com to get a secure purchase link generated and then emailed to you. Here you may pay with a credit card online, by phone, or by fax.
  • Bank Transfer:
  • If purchasing our products through PayPal or via a secure purchase link is not possible for you, then you may contact us to get bank information for a wire transfer. Note that you are responsible for any bank transfer fees.
  • If you do not specify one currency from USD, HKD, JPY, or EUR, we will take USD as the default payment currency.
  • SHAREPOINTBOOST DOES NOT ACCEPT CORPORATE OR PERSONAL CHECKS. PLEASE USE PAYPAL, SECURE PURCHASE LINK OR BANK TRANSFER TO PURCHASE OUR PRODUCTS.
• What is SharePointBoost's refund policy?
  • A request for a refund will only be granted if it is received BEFORE the license code has been sent. Once SharePointBoost has sent you a license code, the sale is considered final. We recommend that you take advantage of the 30-day trial period to download and test the product. This should allow you to fully test and make sure the product meets your needs before making a final purchase decision.
• Does SharePointBoost offer a discount for non-profit organizations, government agencies, or educational institutions?
  • Yes, SharePointBoost can offer discount on condition that you can provide proof that your organization is a registered non-profit, please contact sales@sharepointboost.com for the discount.