Last week we posted the first preview of Highrise. In that preview we introduced the product in broad strokes. With each additional preview we’ll be covering one facet of Highrise in detail.
With preview 2 we’ll be focusing on permissions and groups.
The “keepshare” scenario
Highrise is a shared contact manager. That means that everyone in your organization can use it to keep their contacts and 
contact history together online. While that’s convenient, it does bring up some visibility questions. There are things you may want to keep to yourself and other things you may want to share with others. We call this scenario “keepshare.”
What if you have someone in your contacts list that other people in your company shouldn’t know about? An investor or a sensitive contact that hasn’t been made public yet. Or what if only some people should be able to see the person? 
There’s also the case where someone should be visible to everyone, but certain notes about that person should only be visible to some people. Now what?
The solution
We spent a lot of time on permissions in Highrise. The bulk of the code in Highrise is permissions code. We tried a lot of different systems and a lot of different concepts. We finally went with the clearest solution from a customer experience standpoint. 
There were technically superior solutions, but they required too much mental overhead to understand. Clarity is key so we aimed for that.
In the spirit of open collaboration we wanted everything to default to “Everyone.” If something is in the system, everyone in the system can see it by default. However, you can also make something visible so “Only I can” see it. Or you can “Select a group” of people to see it. Or you can “Select people” to see it. “Groups” are predefined, “people” are are selected on the fly. 
Groups
One of the things we realized early on is that it would be useful to be able to predefine groups of people to use with the permission system. For example, there may be situations where “Partners” should be able to see one thing, “Investors” another thing, the “Sales” department something else, and the “Board of Directors” some other things. Highrise Groups lets you add people to groups so you can quickly set permissions on people, notes, companies, and cases (more on cases in another post).
Stay tuned for the next Highrise preview.
Sign up to have a chance at a Golden Ticket
As we get closer to launch we’ll begin issuing “golden tickets.” Golden ticket holders will have access to sign-up for Highrise prior to the public launch. To sign up for a chance at a golden ticket, be sure to sign up for the Highrise announcement list.
Ross Hill
on 20 Feb 07Looking good so far :)
qwerty
on 20 Feb 07Permissions are a very interesting topic. I am assuming that you try to implement the simplest system possible and I wonder whether having groups was not enough and why you needed “Select people ..” as well. Whenever you need this, don’t you think that your groups are ill-defined and that you are about to leave the workflow that is implicitly implemented by groups?
JF
on 20 Feb 07Whenever you need this, don’t you think that your groups are ill-defined and that you are about to leave the workflow that is implicitly implemented by groups?
There are lots of cases when you’d want to build a temporary ad-hoc group on the fly. In a perfect world people would always be thinking ahead and prepared. The actual world is more chaotic.
Of course if you want to define all your groups up front and never build a temporary group on the fly you are free to do so. There is no limit to the number of groups you can have. How you use groups is up to you.
Keith Mancuso
on 20 Feb 07Simple yet powerful. Covers all my bases…i cant wait!
matt
on 20 Feb 07Hm. Why do you limit it to a single group vs. multiple groups? Or can groups be made up of other groups? A good typical example I would think would be “Sales” and “Marketing”. Would the suggestion then be to create a group called “SalesAndMarketing”? In typical permissions models, you would have a group made of multiple groups which would then simply inherit the users (so if I have a new hire in sales, I don’t have to add him to sales and salesandmarketing).
Caleb Elston
on 20 Feb 07Thanks for the preview! Keep them coming. It is nice to see you are using some colored gifs in the interface rather than simple text ”+” &”-”.
Des Traynor
on 20 Feb 07Looks really good.
Something I am wondering about, is how does it deal with duplicate entries while maintaining privacy.
e.g. if John has contact with Des Traynor ([email protected]) , and Ryan has contact with Des Traynor ([email protected]), and both people want their communication kept private, will there be 2 Des Traynors recorded by the app?
(I realise this is a contrived scenario, but I am just thinking about how tricky the code must get to allow for all these odd circumstances.)
gwg
on 20 Feb 07I’m also curious which permission level “wins” for a contact.
I say that Des is a “only me” contact, but my assistant says “Everyone” can see Des… Who wins?
Gary
on 20 Feb 07Looks great, can’t wait to check it out.
There are lots of cases when you’d want to build a temporary ad-hoc group on the fly.
When I do that, does it create a new entry in the groups list, for easy future selection? So the first time I select an ad hoc group, next time “Jeff,Sam,Marcus,Laura” are in a new group that I can always select, or edit like a normal group?
Bill
on 20 Feb 07I hope you’ve solved the permissions problem in a way you’re happy with, it’s not easy. One of the thorniest and least enjoyable design I ever worked on was dragged down for months and months around permissions issues. You get people saying, just make it like Windows groups (or Unix, or whatever), without realizing how complex and broken those models can be.
And as soon as your own system needs something a little unusual, you spiral off into a world of exceptions, edge cases, and baffling implications that are almost impossible to solve.
Worst, “permissions” are rarely the actual value in your product—nobody buys a CMS so they can set permissions on their content all day, they buy it to publish a website.
JF
on 20 Feb 07Des, you can have as many copies of a person in Highrise as you want, but you can also merge copies into a single record. So you can have 2 versions of John Doe or 1 version of John Doe.
If you can’t see the copies then you don’t know they exist. You can never merge something you can’t see. This maintains proper privacy based on your access level. “Winner” and “Loser” status flows naturally based on your access.
It’s harder to explain when you can’t see it working. Stay tuned.
JF
on 20 Feb 07Bill you are absolutely right. We originally spent a lot of time worrying about things and cases and conditions that were contrived. Yes, these super complex cases may show up for some people, but we’d rather everything is clear and easy 95% of the time and impossible 5% of the time. Software doesn’t need to fit into every situation. Sometimes it just can’t do something. That’s OK.
One day we just said (screamed) “Fuck it. What actually makes sense based on common use cases?” instead of “But what if Person A needs to see this, Person B this, but A is part of Group C and B is part of Group A even though Group A has the same members as Group C.” Blah blah blah. Dreaming up edge cases is a sure fire way to waste a month of development time and burn buckets of morale.
We’re very happy with the final system we developed. It’s simple on the surface, it makes sense, it handles most of the common cases effortlessly, and it says “sorry, no can do” to the convoluted complex stuff that really doesn’t have a place in this product anyway.
Joe Grossberg
on 20 Feb 07“Remove” links make me nervous. How are you solving the problem of graceful degradation vs. making sure a browser tool doesn’t “prefetch” all those links?
Tim
on 20 Feb 07Who is the target market for an application like this? It seems that 37signals products are targeted at individuals and small business.
A contact manager is destined only for use by middle (100+ employee) to large size corporations.
Is that the market 37signals really wants to target?
SS
on 20 Feb 07Joe, the Remove link takes you to a confirmation page that requires a form to be submitted. Regarding “graceful degradation,” Highrise requires JavaScript, just like all of our other applications.
Dan Boland
on 20 Feb 07I say that Des is a “only me” contact, but my assistant says “Everyone” can see Des… Who wins?
Whoever has permissions to grant permissions. ;)
gwg
on 20 Feb 07I’m sure it’ll be fine, it’s just a question I struggle to answer when sketching my own apps. :)
Eddie
on 20 Feb 07I realize that basecamp != highrise, but this post just seems odd in comparision to the previous post on “control vs. communication.” Could you at least go into why you chose permissions and controls as one of the first features to bring to light in highrise and how the decisions work in conjunction with your philosophies. Can you talk more about why highrise leans more towards control and basecamp leans more to “communication”
For what it’s worth, I did have a sacrastic, jerk-sounding reply that I’ll through in for good humor: ...why can’t you just respectfully ask them not to look?Mark Gallagher
on 20 Feb 07This is tricky stuff.
From my experience, any permissions functionality that is intended for a broad audience (tech and non-tech) must be very, very simple. Just the word “permissions” scares off the business people.
Worked on a sharepoint group collaboration pilot in a large corporate environment. The complicated permissions killed it for the business people. Too complicated. The pilot failed.
Also, sharing your contacts is tricky. From my experience most small business people do this in many informal ways (email, etc.) that work pretty well for them. In a large corporate, complicated environment there is more process and control around customer contact management but these large corporate clients (right or wrong) only use software or web apps from the big companies (IBM, Microsoft) and would probably not buy from a vendor like 37s because they fear not enough security and accountability from small vendors.
Just some quick thoughts.
Tim
on 20 Feb 07@Mark Gallagher
That’s exactly why asked who is 37signals target market for this application.
Large corporations purchase software from vendors they know will be around for years. This is mainly for support, and continues to be the reason why large corporations will NOT use open source software unless they are paying a major player in the market for software support.
Also, for a large corporation to use a hosted service, they must have a tremendous amount of faith/confidence in the company. This is typically gained merely by being in the market for years, and it also helps if the vendor is also public. This is so that it’s customers can buy into the company, and or gained confidence from market regulations on the business.
JF
on 20 Feb 07First off, many of the world’s largest corporations, organizations, and institutions have Basecamp, Backpack, or Campfire accounts. Small teams in these large organizations use our stuff all the time. They usually use our products because they other products they are mandated to use either don’t work, are too confusing, or don’t apply to their situation.
We don’t sell products to “Big Huge Company, Inc” we sell products to the marketing department of Big Huge Company, Inc. We don’t want Big Huge Company, Inc. to mandate use of our products across 12,000 employees. That’s not what our products are for. But the 7-person marketing team working on the new ad campaign for a new product release loves using Basecamp and Campfire to get their project done right.
Who is the target market for an application like this? It seems that 37signals products are targeted at individuals and small business.
Small business, small teams, and individuals is our market. Highrise is specifically designed and perfectly suited for these groups.
A contact manager is destined only for use by middle (100+ employee) to large size corporations.
We disagree.
Mark Gallagher
on 20 Feb 07I’m just saying the need for better and easier to use contact management tools is in the large corporate space where there is more process and control. I think this is different and will be more challenging for you than your other project management tools.
And yes, the marketing dapartment of a big company can buy your fine tools by expensing them as a montyly service (because your products are so innexpensive) and work around the IT purchasing guidelines that would probably disallow it as non-standard.
I just don’t sense small teams and small business people are complaining about needing a better tool for contact management. They manage that in many simple and informal ways (their head, their email, on paper and probably several other tools) and think that it works fine for them.
But I could be wrong.
Mark
Ed C.
on 20 Feb 07I think this is a great, clean approach to permissions. Though I’m curious how you will handle “exceptions”?
For example, would it possible to allow the “Sales” Group to see a Contact, and an additional Person (or Persons), like “Bob The Contractor” (who maybe shouldn’t shouldn’t have access to everyone available to the Sales group)
Sam Granieri
on 20 Feb 07Will Highrise be integrated into basecamp like writeboard and campfire? Also, how much is it going to cost?
JF
on 20 Feb 07Pricing will be available when the product is available.
Kiere El-Shafie
on 20 Feb 07Mark, there are plenty of small business that embrace technology. Not because it is mandated to them, but because they recognize it’s value. I am a partner in a small catering company that only has 4 people and we are dying for an app like Highrise. We are two couples in two households and only one of us is the point person for the business, but all of us need to see the contacts and track any additional contact with our customers. I am also the Director of Technology for a medium-size home builder. I certainly don’t want to roll-out one of the CRM apps that I have tried as an IT Director for my small business because they are WAY too complex.
I think 37s is going to do VERY WELL with this app. Small businesses need good technology that they can afford. Not SharePoint or SalesLogix or whatever… and certainly not paper (yikes!!!). ;-)
Mimo
on 20 Feb 07This is so true. Humans often like to think ahead and handle all the problems of today and the future. We often aren’t patient enough to wait the future to hapen.
Jeff Atwood
on 20 Feb 07Golden Ticket? for a freakin’ CRM app? That’s a stretch.
Since when is a web-based CRM app comparable to the excitement of a magical chocolate factory?
JF
on 20 Feb 07Since when is a web-based CRM app comparable to the excitement of a magical chocolate factory?
Since today Jeff! Since today!
Nick Toye
on 20 Feb 07Well I hope its better than the “Magical Chocolate Factory” ride at Alton Towers. :)
Merul
on 20 Feb 07Eddie,
Glad it’s not just me that took a double-take :-)
Eddie
on 20 Feb 07Merul- I’m surprised we’re this far into comments and we’re the only two bringing this up. (I guess the troll hats must have warded off all the haters afterall)
I attribute the “non-mention” to (what I presume are) the different goals of the two applications, although I’m just giving them the benefit of the doubt on that. I find it hard to believe its’ not even worth mentioning something along the lines of “we feel permissions are a key part of Highrise and not part of Basecamp because….”
Especially since the Control vs. Communication post expressed a desire to reduce control even more than it currently is. What’s different about Highrise’s audience that needs “control” than Basecamps which fosters “communication?”
Or, to put a finer point on it…...Why do people collaborations require control but project collaborations do not?
Mike Papageorge
on 20 Feb 07Nice stuff, programming permissions is an interesting challenge for we programming types, and even more so to get it right and make it simple on the interface side of things. Looking forward to seeing this in action.
The merging of contacts and stuff also seems like an interesting programming challenge!
JF
on 20 Feb 07Eddie and Merul: Basecamp and Highrise are entirely different products with entirely different use cases. Both are about communication and both encourage it. Basecamp has one kind of permissions and Highrise has another kind. Each suits their product properly.
Anonymous Coward
on 20 Feb 07Is it just inherently obvious to everyone that CRM requires tighter control than Project Management? I guess so since I’m (nearly) the only one that seems to have noticed. But can’t I make the same arguments you’ve listed here (the keepshare scenario) for project management? And conversely, can’t I just tell my team members not to look at my contact list? “What are they snooping around my contact list for? That’s rude and unprofessional…”
Eddie
on 20 Feb 07....me
JF
on 20 Feb 07Because they are different products entirely. Different data, different models, different user/people distinctions, different tools, different features, different uses. The Highrise permissions wouldn’t work in Basecamp and the Basecamp permissions wouldn’t work in Highrise.
That’s all that I can say at this time.
Mark Gallagher
on 20 Feb 07Kiere,
Many good points. Thanks for opening my eyes.
Mark
Eddie
on 20 Feb 07Ok, I give up. The previous post was about communicating and trusting and respecting people. On each end of your product, whatever it may be, is a person that needs to collaborate with another person regardless of data, models, users/people, tools, features, and uses.
Controls have nothing to do with all those aspects and everything to do with people My only question was was was different about the people in this case (yeah I know they’re different) but clearly this is a question that just seems ridiculous to ask.
But with an introduction like:
...can you blame me for drawing parallels?
JF
on 20 Feb 07Eddie, I’m not blaming you for anything. I never suggested that your question was ridiculous either.
The answer now is the same answer I gave 3 times before: They are different products and require different permissions solutions. Both products default to openness and encourage communication. Basecamp has relevant controls and Highrise has relevant controls. The controls are different because the products are different.
There’s really nothing more to say about it.
Vishi
on 20 Feb 07A few questions:
1) Can all users edit everything they see or does the creator have some special permissions?
2) One day I see a contact and the other day some one removed my permission. Can I see the history of changes for a contact to see whom to contact to get my access back?
Would love to see the copy/merge feature and how its integrated with sharing/unsharing parts of a contact.
Emperor's New Clothes
on 20 Feb 07I’m flabbergasted at the ‘much ado about nothing’ exposed in this post. And the way people who commented about it just lap it up, as if it’s the second coming? Give me a break.
What’s so innovative and ingenious in offering the ACL range from ‘everyone’ to ‘select people’ all the way down to ‘me only’? Isn’t that the way anyone would do it? Actually, is there a different way to do it? I doubt it.
Now, had you come up with a different way to do it, I’d be impressed. But you can’t. And so I simply don’t see what’s the big lesson here.
This unwarranted hoopla made me wonder what’s next? 37signals releases a product that lets people upload images? And then tag the uploaded images? Slow down, I can’t keep up with the breakneck pace, it’s making me dizzy and giddy with excitement!
I want that “golden ticket” so badly now!
JF
on 20 Feb 07Clothier, no one said this was innovative or ingenious. We’re just sharing the solution we came up with.
Actually, is there a different way to do it? I doubt it.
There are plenty. Just look around. Most are terribly complex and confusing.
Anonymous Coward
on 20 Feb 07@Eddie: I can very easily understand why information should be hidden on a relationship manager but not a project manager. It’s about respecting the privacy of those outside of our team.
I work at a NonProfit, and when doing fundraising, sometimes I develop enough of a relationship with a donor that I might know things that they don’t want my whole team to know. So, to respect their privacy while still maintaining enough information for me to maintain a good relationship, I might put information under their entry like “remember to ask about his cancer treatments.” That’s something I would keep private, because I don’t want my boss (who the donor hasn’t told) to ask about the information.
I can’t hurt the project by communicating information about the project to my coworkers, but I can hurt a person by communicating information without their permission.
Nick Toye
on 20 Feb 07I hate the way people feel compelled to comment negatively about a product. If you don’t like it go away. If you are not going to use it, then also go away. But without actually knowing anything about a product why not save the comments till you have tested the product…and then if you still don’t like it, go away.
I think many of us are excited about High Rise because of the form that 37 Signals have shown is in the past. There isn’t a tool I would use to replace Basecamp, it does what I need, but for me its the simplicity that it offers and that is I assume going to be a major selling point for High Rise.
David Smit
on 21 Feb 07The way you implemented your security is vary interesting. I can’t help to wonder if the “Everyone” group will burn people and you guys though like it has burner Microsoft…
In my experience if security is left to people to put on documents or files or contacts they rarely do even if it’s sensitive information.
Interesting constaint…
Anonymous Coward
on 21 Feb 07David Smit: What?
Dave Rosen
on 21 Feb 07This is going to revolutionize everything for us. Thanks.
Anson
on 21 Feb 07Nick, I think it’s natural reaction to this sort of problem/solution post. Many people have come up against this problem in the past and found many solutions, including something like the 37s’ one.
These type of posts tend to come across as a challenge, whether intentional or not. “Here’s what we think is the best solution, see if you can break it”. But really, I think 37s’ are set on this solution so it’s almost trolling—an invitation to post an alternative solution for them to shoot down.
I’m not sure whether these posts are supposed to be a conversation or not. My hunch is not really—I don’t feel like at this point JF & co. are willing to re-think this solution based on a comment.
Mark
on 21 Feb 07I’d be interested to know how you came up with the decision to default a contact and their details to “everyone” instead of “only me”.
I understand the whole concept of “open collaboration”, but CRM and sales revolves heavily around the concept of building a 1:1 relationship and trust. As evidenced by the example a few comments up about the client undergoing cancer treatments, this is and should be treated as privileged information that should only be made public to everyone if and when the contact deems appropriate.
I understand that a contact is not going to reveal this kind of personal information (typically) in a first meeting where his details are first entered into the CRM database; but if I as a co-worker saw that said client’s details were initially available to me, and now are not because he has revealed some information that should be private (but remembered)—doesn’t equate to you now keeping secrets from me and start the breakdown of trust between you and I?
Scott Meade
on 21 Feb 07Anonymous Coward 20 Feb 07 @Eddie: I can very easily understand why information should be hidden on a relationship manager but not a project manager. It’s about respecting the privacy of those outside of our team.
But that is just the point some people made about Basecamp permissions. Who says people are not using Basecamp to track information about people outside of the team? If you are planning a fundraiser in Basecamp, don’t you think Basecamp users thought – “it would be handy to put information about donors in the planning for this fundraiser event, but I don’t want everyone to see it”?
Anonymous Coward
on 21 Feb 07Mark who said anything about CRM? I don’t think 37signals has mentioned CRM once in Preview 1 or Preview 2 of Highrise. I’d be careful to overlay your own expectations of what CRM is with what Highrise is.
Caleb Elston
on 21 Feb 07I don’t know why so many people are so concerned about the fringe 1%, it doesn’t really matter! I use my 8” Wusthof chefs knife every single day, I use my food processor once or twice a year. I would argue the current CRM tools are food processors, they slice, dice, chop, shred, chop, and puree, but they are a pain to use. My knife cannot do everything, but I would take my knife over the food processor any day of the week.
Scott Meade
on 21 Feb 07Anonymous Coward: Folks are thinking CRM because 37s originally called Sunrise their “CRM tool for small business”.
http://www.37signals.com/svn/archives2/sunrise_37signals_crm_tool_for_small_business_is_coming_soon.php
Anonymous Coward
on 21 Feb 07Scott that was well over 13 months ago. If 37signals wanted to evoke CRM I’m sure they would have mentioned it in Preview 1 or Preview 1 within the past week.
JF
on 21 Feb 07Caleb, I like that.
Scott M
on 21 Feb 07Caleb makes a good point – I like it too. We are wondering though if his reference to “current CRM tools” is irrelevant in regard to Highrise. Is Highrise competing with current CRM tools?
Scott M
on 21 Feb 07One final note and then I’ll stop eating up space – I like the comment in Jason’s post that “Clarity is key”. There is so much power in clarity: satisfied customers, lower support efforts, less frustration, less disconnect between expectation and performance, etc. It’s too easy for a software company to burn through a ton of effort in the name of features at the cost of clarity, and then find themselves with disgruntled users, heavy support costs, and a disjointed feature base.
Caleb Elston
on 21 Feb 07I would say it is as relevant as a food processor is to my 8” Wusthof chefs knife. Sure, they both cut food, but would you really compare them the way you are trying to compare current CRM to Highrise? It just doesn’t jive. They both have their place; one is highly specialized and has a steep use curve, where the other (I suspect) will be versitle and allow the user to make the tool really shine. The simple knife in a trained chefs hands is far more accurate and precise than the food processor could ever hope to be.
JS
on 21 Feb 07The prices on your other products are too high for me! Maybe I’m just spoiled by free google apps but I’d rather have a few text ads on the side than pay that much. You probably know better and have someone crunching the numbers but that’s my 2cents.
Anonymous Coward
on 21 Feb 07@JS I suspect they’re making good money from the people that can afford to use their products, and ad support would spoil their clean interface.
You can have 100,000 paying customers on a responsive system, or 10,000,000 free use customers on a sluggish system – I’d rather be among the 100,000 even tho I’m not.
Hugues Peeters
on 21 Feb 07If you allow me a comment, the icon used to remove a select line in the sub section of “select people” is a bit ambiguous. This sign is closer to “forbidden” than to “delete”.
In this specific case, the problem is not too serious, as the “plus” icon beside helps to infer the meaning of the red icon. But, left alone, it could have some ambiguity.
A side question: How the real “forbidden” icon looks like, then ?
JS
on 21 Feb 07@Anonymous Coward – yeah, that’s why I said “you probably know better and have someone crunching the numbers.”
JS
on 21 Feb 07also, google’s products are hardly sluggish.
nakliyat
on 21 Feb 07what do you think google about ?
Jack
on 22 Feb 07so…basically, HighRise is 1/10 of what Outlook already does.
Richard Bird
on 22 Feb 07Much like Basecamp was nothing like most other PMAs that came before it, Highrise is likely to bear little resemblance to what we currently know as CRMs or PIMs. As JF repeats: “It’s different.”
Brian
on 22 Feb 07This sign is closer to “forbidden” than to “delete”.
Hugues, these are the same icons that Apple uses in their Address Book application. As a Mac user, they are familiar to me and I am sure, will make me feel at home using Highrise.
But I can see your point.
Marc Hedlund
on 22 Feb 07I got a full tour of Highrise the other day, and I’m very excited about it. I use Campfire constantly, so if I were ranking 37s apps that would have to come first, but Highrise is right after that. I suspect that I’ll be using it all the time.
What I like most is that it takes my favorite feature from Backpack, reminders, and links them to people. Rather than having to keep an email in my Inbox to remind me to get back in touch with someone, this will let me sweep all that away, and have the Inbox be an Inbox instead of a half-assed to-do list.
Also, I think a lot of productivity tools assume that they’ll replace all the other productivity tools in my life - like how everything you attach to the “home entertainment” complex wants to be the One True Remote Control you use from then on. I like that Highrise assumes the opposite - it doesn’t replace email, it doesn’t replace address books—instead, it works with those tools.
I’m psyched about Highrise. Congrats to the 37s crew on another great product.
J.
on 23 Feb 07I am really looking forward to this product, but I am REALLY hoping that they have thought about email. Not an app to replace email, but an app that understands that 60-90% of client communications happens for better or worse, through email.
I would love to be able to look at a clients account and see reminders of when to follow-up, emails or links to emails I have sent or recieved from them, and all their contact info.
We have looked into many bloated CRM apps and I can’t wait for something simpler.
GMail Premier Account support/integration would be wonderful!
Ed Shull
on 23 Feb 07When I first introduced Basecamp to my employees, I wasn’t confident that I would see people use it. Other introductions to Web apps (like Salesforce.com) went without much use. But within a couple months, the entire organization was using Basecamp with every client. Basecamp makes us better at our jobs. I personally use Backpack for my own projects in my life. It works perfectly for planing my new house. So I am thrilled to see Highrise coming to market.
I know were being treated to little nuggets on info while you put the finishing touches on the product, but I was hoping you could answer two questions.
1. Will there be any exchange between Basecamp and Highrise? For example, can I link a client contact in Highrise to a shared project on Basecamp.
2. Will there be an API?
fred smith
on 23 Feb 07Great stuff. I like the simplicity of the user permissioning system. As discussed above, these types of systems tend to be needlessly complex in many situations.
Could you direct fellow Rails programmers towards any particular user authorization/permissioning scheme or plugin that may have been the basis for this setup?
Keep up the good work.
This discussion is closed.