Thanks to both of you for the quick, detailed and helpful replies. I
was afraid that might be the case (re: separate registrations per
school). How do you get around this with the iOS app? Or do you? Is
there some way that a future build of the OSS / self-hosted options
could somehow "trust" any app that is trusted by the "main" hosted
instance? Or at least a way to opt-in to a trust (i.e., sign in to an
admin page on their own instance and choose from a list of all
registered "partner" apps)?
On Jan 22, 11:14 pm, Cody Cutrer <
c...@instructure.com> wrote:
> Just to be clear, you will only need to register once for all schools that
> are <schoolname>.
instructure.com (and a few that have custom domain names,
> but are still hosted by Instructure). It's just each school that hosts
> their own Canvas will need to be registered with separately.
>
> Cody Cutrer
> Software Engineer
> Instructure, Inc.
>
> On Sun, Jan 22, 2012 at 7:38 PM, Devlin Daley <
dev...@instructure.com>wrote:
>
>
>
>
>
>
>
> >
http://www.instructure.com/partnersto register with Canvas Cloud.
>
> > You would need register with each community installation, since they are
> > completely independent of each other.
>