US 12,493,670 B2
Collaborative user interfaces to configure parameters of API endpoints
Sean Montgomery, Woodland Hills, CA (US); Jacques Antikadjian, Woodland Hills, CA (US); Prakash Chandran, Woodland Hills, CA (US); and Justin Alexander Albrecht, Santa Clarita, CA (US)
Assigned to Xano, Inc., Woodland Hills, CA (US)
Filed by Xano, Inc., Woodland Hills, CA (US)
Filed on Mar. 28, 2023, as Appl. No. 18/127,197.
Prior Publication US 2024/0330418 A1, Oct. 3, 2024
Int. Cl. G06F 21/31 (2013.01); G06F 9/451 (2018.01); G06F 21/62 (2013.01)
CPC G06F 21/31 (2013.01) [G06F 9/451 (2018.02); G06F 21/629 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A system comprising:
a memory; and
at least one hardware processor coupled to the memory and comprising instructions that causes the system to perform operations comprising:
causing display of a graphical user interface (GUI) that comprises a hierarchical permissions interface to define permissions of one or more user activities associated with one or more user accounts, the hierarchical permission interface comprising a display of a plurality of permission menus that include a primary permission menu, and one or more secondary permission menus, each permission menu among the plurality of permission menus comprising a presentation of a set of activity identifiers associated with the one or more user activities;
receiving a definition of a permission value associated with a user activity identified by an activity identifier from among the set of activity identifiers within the primary permission menu, the definition of the permission value comprising a user identifier associated with a user account from among the one or more user accounts, the activity identifier, and the permission value;
identifying a secondary permission menu from among the one or more secondary permission menus responsive to the definition of the permission value within the primary permission menu;
propagating the permission value received within the primary permission menu to the secondary permission menu;
receiving, from a first user via a first client device, an input to define parameters to configure a function of a function stack associated with an Application Programming Interface (API) associated with a workbook corresponding to the secondary permission menu;
receiving, from a second user via a second client device, an input to define parameters associated with the function stack within the workbook while the first user is engaged in defining parameters of the workbook;
determining that the first user is actively engaged in defining parameters of the workbook; and
denying the requested input received from the second user responsive to determining that the first user is actively engaged in defining parameters of the workbook.