Alevtina (Allie) Verbovetskaya
My feedback
12 results found
-
7 votes
An error occurred while saving the comment
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
31 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
15 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
86 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
11 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
100 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
269 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
106 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
35 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
184 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
39 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
-
200 votes
Alevtina (Allie) Verbovetskaya
supported this idea
·
Supporting this strongly from CUNY's perspective. As a consortium running Alma across 26 institutions via 22 IZs, the Developer Network portal creates real security and administrative gaps for us.
Granular role-based access within Alma would let us distinguish between staff who use integrations and those who administer API credentials—a distinction the current portal doesn't support. At CUNY, where we're actively expanding programmatic access to Alma to support library automation and AI-assisted workflows, this matters more every month.
There's no good reason API management should live outside the environment that already handles sensitive configuration with appropriate controls.
This is a security, governance, and usability improvement rolled into one. Strongly in favor.