Should I rename Teams?

I'm looking at using Teams as the basis for a multi-tenant app. The tenants in the app are Schools.

Would you rename the Teams resource everywhere to Schools? Or use it as 'teams' in the app and just switch to calling them 'schools' in the UI?

I think it's easier to Scope the model etc to your new name.  If you update the template I am guessing you would add tons of work to check everything.  I have done that on my app already.  I named a model then regretted it a few days later.  Just updated the routes and the UI and the end users will never know the difference.

Dan Tappin thanks 👍 

That's probably what I would recommend to. It'll make merging updates easier as well. 

I'm in a similar situation, where Accounts (formerly Teams) isn't the right term.  Specifically, I'm trying to figure out how to rename the Accounts links/headers/etc in the Administrate navigation and elsewhere in Administrate.  For the navigation I ended up just modifying the navigation partial, but overriding the views generated by Administrate seems a little more tricky since they share the same show/edit views for every model. Rails I18n translations help, but the default Administrate views don't reference these translations.  Is there a better way to cover all the bases in Administrate?