!p     None*  avers-server(The result of a single module is either 8, which means we continue executing following modules, S which means that the action is allowed and any following modules are skipped, or RejcetRT which means that the action is rejected and following modules are skipped as well. avers-server0Authorization logic is implemented as a list of # actions, each of which we call a module and returns a result ('), which determines what happens next. avers-serverDefines all the authorization points which are used in the server. For each you can supply your own logic. The default is to allow everything. avers-server8Run the authorization logic inside of the Servant monad. avers-server@This doesn't change the result, but allows you to run arbitrary ( actions. This is useful for debugging. avers-server If the given  action returns 4, it is sufficient to pass the authorization check. avers-server The given  action must return ' for this authorization check to pass. avers-server-True if the session created the given object. avers-server~True if the session is the given object. In most cases, a session has full access to the object against which it was created. None -;=>?FSTVNone"#-;<=FST avers-server Convert the  into an T to which the ceredentials refer. That's the object the client is authenticated as.         !"#$+avers-server-0.1.0.1-3DUoAipLWu775nbsV4PPAs Avers.ServerAvers.Server.AuthorizationAvers.Server.InstancesAuthzR ContinueRAllowRRejectRAuthzAuthorizationscreateObjectAuthzlookupObjectAuthzpatchObjectAuthzdeleteObjectAuthzuploadBlobAuthzlookupBlobAuthzlookupBlobContentAuthzdefaultAuthorizationsrunAuthorizationtrace sufficient requisitesessionCreatedObjectsessionIsObjectcredentialsObjId serveAversAPI%avers-0.0.17.1-BBZZMBrFbOrHerdJFs9WAD Avers.TypesAversghc-prim GHC.TypesTrue&avers-api-0.1.0-IjRnWPK65KfJEUrvahIfzLAvers.API.Credentials CredentialsObjId