Grouper Users - Open Discussion List

[David Langenberg <>]

Ok, I see the desire, still, I’m not 100% sold on the docusign thing, esp when you can do the same thing free with GSuite (Forms+AppsScripts) or O365 (Sharepoint + Flow).  How hard would it be to put in special Grouper support for those non-subscription-ish (yeah yeah O365 is not free) instead?  Would those meet the need?

 

Dave

 

--

David Langenberg

Asst Director, Identity Management

The University of Chicago

 

From: Hyzer, Chris <>
Sent: Monday, September 10, 2018 12:51 PM
To: David Langenberg <>; Mailing List <>
Subject: Re: grouper and workflow / access forms

 

 

> From: Greg Haverkamp <>

 

Hellosign is interesting, thanks for mentioning

 

> From: David Langenberg <>

 

> Other than “gee, isn’t this neat?” what’s the use-case? 

 

We have a lot of use cases.  e.g. Someone wants access to warehouse student data, they fill out a form, their manager approves, the data steward approves, gets routed to something automatic or to someone to grant something.  Should also be put in Grouper either way.  We are implementing a new student system and they have a lot of requirements like this.  Its nice to have a paper trail of who requested access, when, who approved it, when it was granted, etc.  Sometimes the form needs comments about why access is needed, maybe some qualifiers like which rows or columns of data to see, etc.

 

Ive been thinking about a built-in way to do this, and I think it needs some sort of form. We could do this with PDFs in S3 buckets but it seems a little clunky and users would have an easier time with something like Docusign or Hellosign, and we wouldnt have to make all the stuff that manages the forms when done...

 

thanks

Chris

 

---

From: David Langenberg <>
Sent: Monday, September 10, 2018 1:19 PM
To: Hyzer, Chris; Mailing List
Subject: RE: grouper and workflow / access forms

 

Other than “gee, isn’t this neat?” what’s the use-case?  I know Docusign is a Net+ offering, but it’s definitely not on a deployment level that, say, Duo or AWS is.  Wouldn’t it be easier (and cheaper) to just extend attestation to include a more robust approval workflow with approvals stored in the grouper audit logs?

 

Dave

 

--

David Langenberg

Asst Director, Identity Management

The University of Chicago

 

From: <> On Behalf Of Hyzer, Chris
Sent: Monday, September 10, 2018 11:36 AM
To: Mailing List <>
Subject: [grouper-users] grouper and workflow / access forms

 

Im not 100% sure it’s the right choice, but hypothetically lets say we integrated Grouper with Docusign.

 

- Someone clicks on a form in the Grouper UI

- It calls a Docusign API to setup an instance of the form

- User fills out basic form fields and e-signs the document

- The approvers at various roles would be sourced from groups (e.g. the student-data steward group [registrar]).  One from each group signs the form

- At the end the requestor would be added to a group or groups

- Docusign stores the history of the forms

 

I don’t know if they have discounts for higherEd/nonprofit, but it seems like the cost for this would be for the Basic API, about $1/form ($600/year for 500 forms/year) or ($5k/year for 6k forms/year)

 

https://www.docusign.com/products-and-pricing/api-plans

 

Might need to buy some user licenses to make/manage forms: ($1k for 2-3 users depending on standard or pro)

 

https://www.docusign.com/products-and-pricing

 

Who would be interested in using this if we integrated with Docusign?  Any other ideas for forms/workflow products where the licensing is reasonable and there is a full featured REST API?  We would try to make this pluggable of course…

 

Thanks

Chris

 

 

 

 

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature