Binder management

Binders are used in Zefort to control the rights of users or groups of users to view and / or edit agreements.

Video transcription

Hi, in this video, we’ll look at binders


and how to use them to control user access.


You can find binders on the left here.


Now in Zefort you can have an unlimited number of binders


and you can also build a hierarchy that’s unlimited in scope.


So you can have as many binders


within as many binders as you want.


Let’s just take a look at that.


Clicking on the onboarding binder now.


You’ll see that there are three


binders within this one binder.


Now, within each of these binders,


I could have more binders,


but for now, I don’t.


Binders are use to control access rights.


So returning to the root.


We’ll just go over here to where there are three dots,


open this


and click on permissions.


This allows us to add users,


remove users…


I just remove this permission.


So we can click up here on Add Group or Add user.


User Jane Miller.




we’ll give her full permission.


Have three tiers of permissions in Zefort.


View, edit and full.


View means view.


In that case, the user can view all the contracts within a binder.


Edit gives them permission to bring new contracts into the binder


and edit the information of the contracts.


And full also allows them to delete contracts


from the binder and the binder itself.


Add user.


So the difference between edit and full


is that full users can also delete.


So now if we go and look in the binder,


we’ll find that.


In example one


we have inherited


Jane Miller.


By default, user permissions are inherited


from the root binder.


And in this case, Jane Miller has inherited the full rights


from the on boarding binder.


Now, for these two examples I’ve turned inheritance off.


In this example two


only I have permission to look at this binder


and inheritance is turned off.


In example three I’ve turned inheritance off,


but I’ve chosen to give John Smith


a view permission for this binder.


This means that John doesn’t have access to the root binder,


but from this example three


and any binders I choose to create within example three,


John will inherit the view permission.


However, I can also turn inheritance off


for any future binders.


So by default, inheritance is on,


but you can turn it off whenever you want.


Heading back to the root.


If you want to know more about binders


and how to use them in different scenarios and situations.


Click on the how to video.


There’s roughly a six minute video


outlining this in slightly better detail


than I’m able to give here.


Binders can also be moved and merged,


so here we can move them to another binder.


Or we can choose to merge them with another binder.


From these three dots you can also look at email inboxes.


Now this is an option,


so your subscription may not include this.


But if we open up here,


we get the email address


which means we can send contracts via email into binders directly.


And this was binders.