IP Library Granted Patent US 12,513,146
Granted Patent B1
US 12,513,146 · App. 18/484,036 · Granted Dec 30, 2025

Creating input tables accessible by multiple account roles

Inventors: Stipo Josipovic (San Francisco, CA); Gregory G. Owen (San Mateo, CA)
Assignee: SIGMA COMPUTING, INC.
H04L63/10
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 12,513,146
App. No.
18/484,036
Granted
Dec 30, 2025
Kind
B1
Abstract

Creating input tables accessible by multiple account roles including receiving, from a client computing system by a data visualizer, a request to create an input table at a destination location on a cloud-based data warehouse, wherein the request is associated with a first account role; determining, by the data visualizer, that the first account role has access to the destination location based on a set of permissions associated with the destination location; and creating, on the cloud-based data warehouse by the data visualizer, the input table that inherits the set of permissions from the destination location on the cloud-based data warehouse.

Claims (37)

1 . A method for creating input tables accessible by multiple account roles, the method comprising:

receiving, from a client computing system by a data visualizer residing on an intermediary computing system between the client computing system and a cloud-based data warehouse, a request to create an input table at a destination location on the cloud-based data warehouse, wherein the request is associated with a first account role assigned to a first user account;

determining, by the data visualizer, that the first account role has access to the destination location based on a set of permissions associated with the destination location; and

creating, on the cloud-based data warehouse by the data visualizer, the input table that inherits the set of permissions from the destination location on the cloud-based data warehouse.

2 . The method of claim 1 , further comprising:

recording the creation of the input table to an audit log using a data visualizer service account.

3 . The method of claim 1 , wherein the set of permissions associated with the destination location indicate that both the first account role and a second account role are authorized to write to the destination location.

4 . The method of claim 1 , wherein the input table created within the destination location on the cloud-based data warehouse is accessible by a second account role.

5 . The method of claim 4 , wherein the input table within the destination location is accessible to a user account assigned to the second account role and not assigned to the first account role.

6 . The method of claim 1 , wherein the request is received using an identity provider account, and wherein the identity provider account provides a first authentication token used to access the data visualizer and a second authentication token used to access the cloud-based data warehouse.

7 . The method of claim 1 , wherein determining that the first account role has access to the destination location comprises:

retrieving, from the cloud-based data warehouse, a set of destination locations accessible by the first account role;

presenting, on the client computing system, the set of destination locations accessible by the first account role; and

receiving a selection of the destination location from the set of destination locations accessible by the first account role.

8 . The method of claim 1 , wherein creating the input table that inherits the set of permissions from the destination location comprises generating a structured database statement in a query language targeting the cloud-based data warehouse to generate the input table within the destination location.

9 . The method of claim 1 , wherein the request comprises a name of at least one column to be created in the input table.

10 . The method of claim 1 , wherein the data visualizer is on an intermediary computing system between the client computing system and the cloud-based data warehouse.

11 . An apparatus for creating input tables accessible by multiple account roles, the apparatus residing on an intermediary computing system between a client computing system and a cloud-based data warehouse, the apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:

receiving, from the client computing system, a request to create an input table at a destination location on the cloud-based data warehouse, wherein the request is associated with a first account role assigned to a first user account;

determining that the first account role has access to the destination location based on a set of permissions associated with the destination location; and

creating, on the cloud-based data warehouse, the input table that inherits the set of permissions from the destination location on the cloud-based data warehouse.

12 . The apparatus of claim 11 , wherein the computer program instructions further cause the apparatus to carry out the steps of:

recording the creation of the input table to an audit log using a data visualizer service account.

13 . The apparatus of claim 11 , wherein the set of permissions associated with the destination location indicate that both the first account role and a second account role are authorized to write to the destination location.

14 . The apparatus of claim 11 , wherein the input table created within the destination location on the cloud-based data warehouse is accessible by a second account role.

15 . The apparatus of claim 14 , wherein the input table within the destination location is accessible to a user account assigned to the second account role and not assigned to the first account role.

16 . The apparatus of claim 11 , wherein the request is received using an identity provider account, and wherein the identity provider account provides a first authentication token used to access a data visualizer and a second authentication token used to access the cloud-based data warehouse.

17 . The apparatus of claim 11 , wherein determining that the first account role has access to the destination location comprises:

retrieving, from the cloud-based data warehouse, a set of destination locations accessible by the first account role;

presenting, on the client computing system, the set of destination locations accessible by the first account role; and

receiving a selection of the destination location from the set of destination locations accessible by the first account role.

18 . The apparatus of claim 11 , wherein creating the input table that inherits the set of permissions from the destination location comprises generating a structured database statement in a query language targeting the cloud-based data warehouse to generate the input table within the destination location.

19 . The apparatus of claim 11 , wherein the request comprises a name of at least one column to be created in the input table.

20 . A computer program product for creating input tables accessible by multiple account roles, the computer program product disposed upon a computer readable storage medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

receiving, from a client computing system by a data visualizer that intermediates between the client computing system and a cloud-based data warehouse, a request to create an input table at a destination location on the cloud-based data warehouse, wherein the request is associated with a first account role assigned to a first user account;

determining that the first account role has access to the destination location based on a set of permissions associated with the destination location; and

creating, on the cloud-based data warehouse, the input table that inherits the set of permissions from the destination location on the cloud-based data warehouse.

Assignments (2)
SUPPLEMENT NO. 1 TO INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Feb 23, 2026
From: SIGMA COMPUTING, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 074971/0863 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2023
From: JOSIPOVIC, STIPO; OWEN, GREGORY G.
To: SIGMA COMPUTING, INC.
Reel/Frame 065173/0522 →
Continuity (2)
Continuation In Part 17749329 · May 20, 2022
Continuation 17015579 · Sep 9, 2020
References Cited (41)
US 6289431B1 · Bigbee · 2001 [cited by examiner]
US 7886048B1 · Holland · 2011 [cited by examiner]
US 9176966B2 · Silverstein · 2015 [cited by examiner]
US 9721038B1 · Xiang · 2017 [cited by examiner]
US 10043591B1 · LaBorde · 2018 [cited by examiner]
US 10635093B2 · Miller · 2020 [cited by examiner]
US 10681073B2 · Sofer · 2020 [cited by examiner]
US 10942900B2 · Rathinagiri · 2021 [cited by examiner]
US 11363024B2 · Owen · 2022 [cited by examiner]
US 12039066B1 · Sharma · 2024 [cited by examiner]
US 20050144195A1 · Hesselink · 2005 [cited by examiner]
US 20120047162A1 · Guglietti · 2012 [cited by examiner]
US 20130187926A1 · Silverstein · 2013 [cited by examiner]
US 20140129936A1 · Richards · 2014 [cited by examiner]
US 20140164008A1 · Gordon · 2014 [cited by examiner]
US 20150281248A1 · Obbard · 2015 [cited by examiner]
US 20160019281A1 · Hariharan et al. · 2016 [cited by applicant]
US 20160373402A1 · Becker · 2016 [cited by examiner]
US 20170126640A1 · Vincent · 2017 [cited by examiner]
US 20170177201A1 · Disdero · 2017 [cited by examiner]
US 20180121566A1 · Filippi · 2018 [cited by examiner]
US 20180181446A1 · Bequet · 2018 [cited by examiner]
US 20180307853A1 · Mehta · 2018 [cited by examiner]
US 20180330114A1 · McGrath · 2018 [cited by examiner]
US 20190101884A1 · Miller · 2019 [cited by examiner]
US 20190101900A1 · Miller · 2019 [cited by examiner]
US 20190101909A1 · Miller · 2019 [cited by examiner]
US 20190102456A1 · Miller · 2019 [cited by examiner]
US 20190146637A1 · Plache · 2019 [cited by examiner]
US 20190207964A1 · Sofer · 2019 [cited by examiner]
US 20200301939A1 · Hollander · 2020 [cited by examiner]
US 20200344233A1 · Lai · 2020 [cited by examiner]
US 20210191629A1 · Vibhor · 2021 [cited by examiner]
US 20210266329A1 · Fuhry · 2021 [cited by examiner]
US 20220078189A1 · Owen · 2022 [cited by examiner]
US 20220278987A1 · Owen · 2022 [cited by examiner]
US 20230138668A1 · Decrop · 2023 [cited by examiner]
US 20230275893A1 · Sharma · 2023 [cited by examiner]
Anonymous, “Understanding Service Accounts,” Cloud Identity and Access Management Documentation, XP055633590, URL: https://web.archive.org/web/20180717204752/https://cloud.google.com/iam/docs/understanding-service-accou… [cited by applicant]
Carter, Peter A., “Implementing Service Accounts for Security,” Securing SQL Server, Apress, Berkeley, CA, XP055872957, ISBN: 978-1-4842-2265-2,pp. 117-128, DOI: 10.1007/978-1-4842-2265-2_7, URL:http://link.springer.com… [cited by applicant]
International Search Report and Written Opinion, PCT/US2021/049444, Jan. 4, 2022, 14 pages. [cited by applicant]