IP Library Granted Patent US 9,195,843
Granted Patent B2
US 9,195,843 · App. 12/958,178 · Granted Nov 24, 2015

Systems and methods for permissioning remote file access via permissioned links

Inventors: Don MacAskill (Los Altos, CA); Chris MacAskill (Mountain View, CA); Brian Strong (San Jose, CA)
Assignee: SMUGMUG, INC.
G06F21/6209G06F2221/2119
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,195,843
App. No.
12/958,178
Granted
Nov 24, 2015
Kind
B2
Abstract

Permissioned links for a novel method of credentialing users and assigning permissions to the user using the link to access repositories holding or intended to hold digital files. The permissioned links comprise a unique identifier that can be correlated to a specific repository of digital files and permission set. Users using the permissioned links for access need not enter a login or password. Moreover, permissioned links are portable, allowing multiple users to access the repository of digital files using the same permissioned link.

Claims (22)

1. A system comprising:

at least one computer making a repository of private remote digital files available to a remote user, the repository of private remote digital files being accessible from remote locations, the repository being permissioned with a first set of permissions and a second set of permissions different from the first set of permissions by an owner of the repository, wherein the repository exists in conjunction with an event, wherein the event comprises at least one sub-event, each sub-event being a repository, wherein each sub-event inherits the permissions of the repository, and wherein the owner communicates to the user a first permissioned link and a second permissioned link for credentialing the remote user that is created upon the repository being permissioned;

a permissioned link database having a table therein correlating a uniform resource indicator (URI) of the first permissioned link and the second permissioned link with the first set of permissions and the second set of permissions, the first set of permissions and the second set of permissions defining anonymous access permissions for use of the private remote digital files in the repository; and

a host for receiving from the user an anonymous request via the first permissioned link and the second permissioned link and for communicating private remote digital files to at least the user based on the first set of permissions or the second set of permissions associated with the first permissioned link or the second permissioned link, wherein the host allows any unregistered user requesting access to the repository with the first permissioned link or the second permissioned link to access the repository according to the first set of permissions or the second set of permissions in the permission set, and wherein the user remains an unregistered user.

2. The system of claim 1 , wherein the first set of permissions and the second set of permissions are both created when the repository is created.

3. The system of claim 1 , wherein the repository contains only sub-events and does not contain private remote digital files.

4. A method comprising:

permitting a first user to cause creation of a repository of private remote digital files, wherein the first user chooses a first set of permissions and a second set of permissions different from the first set of permissions to be associated with a first permissioned link and a second permissioned link, respectively, that is used to remotely and anonymously access the repository of private remote digital files, wherein the repository is a component of an event, wherein each event comprises at least one sub-event, the sub-event being a repository of files, and wherein each sub-event inherits the permissions of the first permissioned link and the second permissioned link;

causing transmission of a communication containing the first permissioned link and the second permissioned link to a second user, wherein the second user is unregistered and remains unregistered with the repository;

receiving from the second user an anonymous request to access private remote digital files associated with the first permissioned link and the second permissioned link;

resolving the first permissioned link and the second permissioned link by correlating the first permissioned link and the second permissioned link with the first set of permissions and the second set of permissions, respectively; and

permitting the second user to access the content associated with the first permissioned link and the second permissioned link according to the permissions in the first set of permissions and the second set or permissions, wherein the first permissioned link and the second permissioned link each comprise at least a unique identifier.

5. The method of claim 4 , further comprising permitting any third user to access the content associated with the first permissioned link and the second permissioned link according to the permissions in the first set of permissions and the second set of permissions if the first permissioned link and the second permissioned link are received from the third user.

6. A non-transitory machine-readable medium having instructions stored thereon comprising:

permitting a first user to cause creation of a repository of private remote digital files, wherein the first user chooses a first set of permissions and a second set of permissions different from the first set of permissions to be associated with a first permissioned link and a second permissioned link, respectively, that is used to remotely and anonymously access the repository, wherein the repository is a component of an event, and wherein each event comprises at least one sub-event, the sub-event being a repository of private remote digital files, and wherein each sub-event inherits the permissions of the first permissioned link and the second permissioned link;

causing transmission of a communication containing the first permissioned link and the second permissioned link to a second user, wherein the second user is unregistered and remains unregistered with the repository;

receiving from the second user an anonymous request to access the private remote digital files associated with the first permissioned link and the second permissioned link;

resolving the permissioned link by correlating the first permissioned link and the second permissioned link with the first set of permissions and the second set of permissions, respectively; and

permitting the second user to access the content associated with the first permissioned link and the second permissioned link according to the permissions in the first set of permissions and the second set of permissions, wherein the first permissioned link and the second permissioned link each comprise at least a unique identifier.

7. The non-transitory machine-readable medium of claim 6 , further comprising permitting any third user to access the content associated with the first permissioned link and the second permissioned link according to the permissions in the first set of permissions and the second set of permissions if the first permissioned link and the second permissioned link are received from the third user.

8. The method of claim 5 , wherein the third user is an unregistered user.

9. The method of claim 7 , wherein the third user is an unregistered user.

Assignments (3)
SECURITY INTEREST Recorded Jul 30, 2025
From: AWES.ME, INC.
To: AVIDBANK
Reel/Frame 071884/0090 →
CHANGE OF NAME Recorded Mar 30, 2022
From: SMUGMUG, INC.
To: AWES.ME, INC.
Reel/Frame 059554/0609 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2013
From: MACASKILL, DON; MACASKILL, CHRIS; STRONG, BRIAN
To: SMUGMUG, INC.
Reel/Frame 030790/0162 →
Continuity (2)
Provisional Application 61265724 · Dec 1, 2009
Related Publication 20110131633A1 · Jun 2, 2011