Browse Prior Art Database

System and method to restrict Cloud SaaS Application Function limits based on co-location

IP.com Disclosure Number: IPCOM000238642D
Publication Date: 2014-Sep-09
Document File: 2 page(s) / 52K

Publishing Venue

The IP.com Prior Art Database

Abstract

A system and method to restrict Cloud Software as a Service (SaaS) Application Function limits based on co-location of other authorized users is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

System and method to restrict Cloud SaaS Application Function limits based on co -location

Disclosed is a system and method to restrict Cloud Software as a Service (SaaS) Application Function limits based on co-location of other authorized users.

Cloud SaaS applications are advantageous for various reasons. The reasons include efficient user provisioning in a multi-tenant environment, provisioning of free and premium services based on charges, and competitively priced with on-premise software for a variety of reasons. There are some document signing solutions which exist today for cloud applications which enable users to co-sign and have a electronic legal document which can be defended in a court of law. In addition, many organizations including the government require approvals of documents by specific set of approvers who need to be co-located. For example, corporation by laws may have provisions to approve building plans by town planning officials located at a pre-determined location.

Disclosed is a SaaS system which has the ability to prevent the use of one or more functions depending on the relative location of two or more users. One embodiment deals with ensuring that two or more authorized individuals are physically (or virtually) co-located so that no one person can edit a document unsupervised or without checks and balances. Another embodiment deals with co-located approvals of various documents or artifacts which need to ensure that the approvers are located at specific locations before the workflow can be completed. The system incorporates methods which determine who is authorized, where they are in relation to each other, and if their relative co-location meets a restrictive policy embedded within the cloud application document.

Example 1

A company's by-laws indicate that by-laws can only be changed when three of the five board members are present in a duly authorized meeting. The system would allow the user using an SaaS document editing cloud application to open the by-laws document and read it or add comments to it but would not allow them to make changes to or add things to the document unless it detected that two other board members were in the same physical location (co-located). Alternatively, if the embedded policy for that document allowed it, the users could be virtually co-located (i.e. they are all logged into a collaborative cloud document sharing tool and 'virtually' present).

Example 2


In a court room setting, legal documentation can be created and edited. There may be cases when decisions are handed down that require the Judge, Plaintiff, Defendant, Jury or any other host of people to be physically present in the room at the time of recording. If the judge were to leave the room or if one of the other required individu...